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-3/

{
  "context": "Tests whether the agent ensures consistency across a suite of MCP tools: consistent parameter naming, ordering, documentation structure, error formats, and organizational patterns.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Consistent parameter names",
      "description": "Similar concepts use the same parameter names across tools (e.g., file_path not filename or path)",
      "max_score": 20
    },
    {
      "name": "Parameter ordering",
      "description": "Parameters follow consistent ordering (required first, optional after)",
      "max_score": 15
    },
    {
      "name": "Documentation structure",
      "description": "All tools follow identical documentation structure (same sections in same order)",
      "max_score": 15
    },
    {
      "name": "Error format",
      "description": "Error documentation uses identical format across all tools",
      "max_score": 15
    },
    {
      "name": "Tool grouping",
      "description": "Related tools share common prefixes for discoverability",
      "max_score": 15
    },
    {
      "name": "Tool index/categorization",
      "description": "Includes a tool index or categorization showing how tools relate",
      "max_score": 10
    },
    {
      "name": "Cross-references",
      "description": "Tools include 'see also' references to related tools",
      "max_score": 10
    }
  ]
}

tile.json