Skip to main content
Glama

get_leagues

Read-only

Discover leagues present in retained events, with retained and upcoming scheduled event counts. Counts do not guarantee current live coverage. Stored DraftKings via ESPN only. Offset pages are not a frozen snapshot.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_leagues"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sportNo
offsetNo
upcoming_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety is covered structurally. The description adds real value beyond that: the data source restriction ("Stored DraftKings via ESPN only") and the warning that offset pages are not a frozen snapshot, which tells the agent results can shift between calls. It stops short of describing the response shape or how counts are computed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with what the tool returns, and no filler. The phrasing is telegraphic in places ("Stored DraftKings via ESPN only"), slightly reducing clarity without wasting words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only discovery tool with no output schema, the description covers data provenance and count caveats adequately. However, with zero schema coverage on four parameters and no explanation of the returned league fields, an agent still lacks what it needs to page or filter confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, so the description must carry the burden and largely does not: limit, sport (with its five-value enum), and upcoming_only are never explained. Only offset behavior is addressed indirectly via "Offset pages are not a frozen snapshot," leaving most parameters ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb plus resource: "Discover leagues present in retained events," and adds that it returns retained and upcoming event counts. This differentiates it from event-listing siblings such as get_events, though the term "retained events" is jargon an agent must infer.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance and no named alternative (e.g., get_sports or get_events), so routing must be inferred from the name alone. The caveat "Counts do not guarantee current live coverage" is a reliability warning, not usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.