list_metricsWhat Muffed can answer on. By default a summary of metric families with their counts and season coverage; pass search or detail:true for individual metric keys. Returns keys and coverage only, never figures.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| detail | No | ||
| search | No | ||
| season | No | ||
| entity_kind | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish read-only, idempotent, and non-destructive behavior. The description adds valuable context about default output format (summary vs detail) and the explicit constraint that only keys and coverage are returned, enhancing transparency beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact, two sentences, with no fluff. It front-loads the purpose and usefully specifies the return scope, all in minimal words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description adequately explains the core functionality and return constraints, but the tool has 5 parameters and no output schema; the description does not sufficiently cover all input dimensions (e.g., what entity_kind filters, what limit does). This leaves gaps for complex queries.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description needed to explain all parameters, but it only clarifies 'search' and 'detail:true'. The semantics of limit, season, and entity_kind are left unaddressed, forcing agents to guess their purposes.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: listing metric families or individual metric keys with coverage information. It explicitly distinguishes itself from metric-value tools by saying 'never figures', which sets it apart from siblings like get_entity_metrics.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explains how to use the tool (default summary vs search/detail for individual keys) but does not explicitly state when to prefer this over alternatives. The 'never figures' limitation implies you'd use another tool for actual values, but no alternative is named.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource or action: entity metrics, metric definitions, leaderboards, comparisons, backfield info, editorial insights, claim verification, and five separate Sleeper league tools each with a clear purpose. No two tools could be easily confused.
All tool names use snake_case and follow a predictable verb-noun pattern (get_, list_, query_, compare_, verify_) with the sleeper_* prefix consistently applied to fantasy-league tools. The naming convention is uniform throughout.
13 tools is within the ideal 3-15 range and matches the server's dual purpose of verified NFL stats and fantasy context. Every tool serves a clear function without redundancy or bloat.
The tool surface comprehensively covers the stated domain: metric retrieval, definitions, listings, leaders, comparisons, backfield context, insights, claim verification, and fantasy league operations. No obvious dead ends or missing core operations.