list_leaguesList supported league ids, market types and periods. No API key required. Use before a fair-value query when you do not already know the allowed ids; do not use it for live prices.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the behavioral transparency burden. It usefully discloses 'No API key required,' and the word 'List' implies a read-only, non-destructive operation. It does not describe response format or pagination, but for a simple metadata endpoint this is sufficient.
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 two concise sentences with no filler. The main purpose is front-loaded, and the usage guidance and auth note are delivered efficiently.
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?
For a parameterless, authentication-free listing tool, the description provides enough context for an agent to call it correctly: what it lists and when to use it. It does not specify the exact output shape, but the nature of the result is clear from the stated content.
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?
The tool has zero parameters, so there is nothing for the description to add beyond the schema. The baseline of 4 for parameterless tools applies, and the description does not introduce confusion about arguments.
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 function with a specific verb and resource: 'List supported league ids, market types and periods.' This differentiates it from siblings by positioning it as a metadata lookup used before fair-value queries, not for live prices.
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 gives explicit when-to-use guidance: 'Use before a fair-value query when you do not already know the allowed ids.' It also provides a clear exclusion: 'do not use it for live prices,' which distinguishes it from price-related sibling tools.
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 has a clearly distinct purpose: describe_* covers meta topics, list_* covers discovery, get_* covers retrieval, and grade is a unique action. The descriptions explicitly cross-reference when to use one tool vs another, such as list_fair_values for discovery and get_fair_value for known outcome ids.
Tool names are overwhelmingly consistent snake_case imperative verb_noun pairs (describe_, get_, list_), and grade is a readable verb-only command. The single deviation from verb_noun is minor and does not create confusion.
Ten tools is well-scoped for the server's purpose: meta/explanation tools, discovery tools, retrieval tools, and a grading action. Each tool earns its place without overlapping or feeling like filler.
The tool surface covers the full read-only workflow: discover supported leagues, list and fetch fair values, retrieve history, grade submitted prices, and understand settlement rules, plans, and authentication. There are no obvious dead ends or missing operations for the stated domain.