CtrlK
BlogDocsLog inGet started
Tessl Logo

finkel/mcp-tool-naming

Guidelines for naming MCP tools, describing parameters, and documenting tools in a language- and framework-agnostic manner

97

1.02x
Quality

Pending

Does it follow best practices?

Impact

97%

1.02x

Average score across 5 eval scenarios

SecuritybySnyk

Pending

The risk profile of this skill

Overview
Eval results
Files

criteria.jsonevals/scenario-1/

{
  "context": "Tests whether the agent follows MCP tool naming conventions: snake_case formatting, domain prefixes, action-oriented verbs, consistency across tools, predictable patterns, and discoverable grouping.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "snake_case formatting",
      "description": "All tool names use lowercase with underscores (no camelCase, PascalCase, or kebab-case)",
      "max_score": 20
    },
    {
      "name": "Domain prefixes",
      "description": "Tools use appropriate domain prefixes (e.g., weather_, file_, db_) to group related functionality",
      "max_score": 20
    },
    {
      "name": "Action-oriented verbs",
      "description": "Tool names start with action verbs (create, read, update, delete, search, validate, get, set, etc.)",
      "max_score": 15
    },
    {
      "name": "Naming consistency",
      "description": "All tools follow the same naming style (no mixing of snake_case, camelCase, etc.)",
      "max_score": 15
    },
    {
      "name": "Predictable patterns",
      "description": "Tool names follow consistent patterns that make them predictable (e.g., <domain>_<action>_<resource>)",
      "max_score": 15
    },
    {
      "name": "Discoverable grouping",
      "description": "Related tools share common prefixes, making them easy to find together",
      "max_score": 15
    }
  ]
}

tile.json