Skip to main content
Glama

get_bookmakers

Read-only

Read stored DraftKings-via-ESPN bookmakers. 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_bookmakers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 safety is covered. The description adds real behavioral context beyond that: capture time and source identifiers are part of the payload, and offset pages are explicitly not a frozen snapshot, warning about consistency across pages. It still says nothing about ordering, result size, or error behavior.

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?

Three short sentences with the resource statement front-loaded, followed by data-fidelity and pagination caveats. Nothing is padded, though 'Preserve capture time and source identifiers' is slightly ambiguous as to whether it instructs the agent or describes returned fields.

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?

With no output schema, the description does hint that responses carry capture time and source identifiers, which is helpful. However, for a paginated, source-specific list tool with two undocumented parameters and no exposure of return shape or pagination termination, it leaves gaps an agent must guess at.

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

Parameters3/5

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

Two parameters exist with 0% schema description coverage, so the description must compensate. It addresses offset indirectly through the 'offset pages are not a frozen snapshot' caveat, which is meaningful semantics, but limit and its 1-200 bounds are never mentioned in the description.

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?

States a specific verb and resource: read stored DraftKings-via-ESPN bookmakers, and the source qualifier distinguishes it from the sibling source-specific tools such as get_fanduel_markets and get_pinnacle_markets. It stops short of explicitly contrasting itself with those siblings, but an agent can identify the resource unambiguously.

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 when-to-use or when-not-to-use guidance and no named alternative among the many sibling tools. The pagination caveat implies a retrieval scenario but leaves the agent to infer when this listing should be preferred over other bookmaker or market tools.

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.