Skip to main content
Glama

get_fanduel_markets

Read-only

Read stored FanDuel non-futures markets and selections. Source-native IDs and separate observation/change/event-read clocks; incomplete capture and no cross-book matching.

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_fanduel_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNo
familyNo
leagueNo
statusNo
event_idNo
market_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, non-destructive, closed-world), yet the description adds real value: 'stored' signals cached rather than live data, 'separate observation/change/event-read clocks' discloses multi-timestamp freshness semantics, 'incomplete capture' warns of data gaps, and 'no cross-book matching' warns that IDs cannot be joined across books. These are non-obvious traits an agent could not derive from the annotations or schema.

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?

Two compact sentences with the core resource statement front-loaded and no filler. The second clause is dense near-jargon ('separate observation/change/event-read clocks') that trades readability for brevity, but nothing is redundant.

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 and no documented parameters, the description should say more about what a returned market/selection record contains and how the 'after'/'limit' paging behaves. The caveats it does provide are high-value, so the definition is serviceable but leaves real gaps for a 7-parameter read tool.

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 seven parameters, so the schema supplies only types, patterns, one enum, and a default. The description clarifies only that IDs are source-native, which touches event_id/market_id but leaves family, league, status, after, and limit unilluminated — notably the 'after' cursor and limit pagination semantics are never explained.

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 FanDuel non-futures markets and selections' — which distinguishes it from generic siblings like get_markets and from other book-specific tools such as get_betrivers_markets or get_pinnacle_markets. The 'non-futures' scope is an explicit boundary, though no sibling is named directly.

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. The agent must infer from the word 'stored' and the book name alone whether to call this versus get_markets or get_odds. 'No cross-book matching' is a data caveat, not a routing instruction.

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.