Skip to main content
Glama

get_sports

Read-only

Read stored DraftKings-via-ESPN sports. Preserve capture time and source identifiers. 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_sports"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: the data is stored rather than live, capture time and source identifiers should be preserved, and offset pages are explicitly not a frozen snapshot (a real pagination-consistency caveat). These additions are valuable but phrased so tersely that the practical implication is only half-explained.

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

Conciseness3/5

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

Three short sentences, front-loaded with the core action, and nothing is padded. However, the terseness crosses into cryptic: "Preserve capture time and source identifiers" gives no object or reason, so the sentence costs the reader more interpretation effort than it saves space.

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?

No output schema exists, so the description would ideally describe the return shape, and it only gestures at it via "capture time and source identifiers." Combined with two undocumented parameters and no usage guidance, the definition is thin for a paging list tool, though its pagination warning partially addresses the most important gotcha.

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% and neither parameter is named in the description; limit and offset are undocumented except through the oblique "offset pages" remark. With low coverage the description should compensate with defaults, bounds, or paging semantics, and it does not (the max of 200 and the 10000 offset cap are nowhere mentioned).

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

Purpose3/5

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

Uses a concrete verb ("Read") and identifies the data domain (stored DraftKings-via-ESPN sports), with "stored" usefully implying archival rather than live data. But the resource noun "sports" is vague — it is unclear whether this returns a list of sports, events, or odds payloads — and nothing distinguishes it from siblings like get_leagues, get_events, or get_odds.

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 or when-not-to-use guidance and no named alternative among the many sibling tools. The sentences present are data-handling instructions (preserve capture time, beware offset paging), not selection guidance, so an agent gets no help choosing this over get_events or get_history.

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.