Skip to main content
Glama

get_outright_odds

Read-only

Read stored FanDuel futures selections and prices. Preserve source-native IDs and clock meanings; incomplete capture, no cross-book matching or live freshness guarantee.

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

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.4/5.0
Behavior4/5

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

Annotations already establish read-only, closed-world, non-destructive behavior, and the description adds genuinely useful caveats: incomplete capture, no cross-book matching, and no live freshness guarantee. The instruction to preserve source-native IDs and clock meanings discloses an important data-fidelity constraint. It still does not describe the response shape or pagination, which keeps it below a 5.

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 sentences, front-loaded with the core action, with the caveats compressed into a single dense clause. The second sentence is telegraphic but every element (incomplete capture, no cross-book matching, no freshness guarantee, ID/clock preservation) carries information.

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 should convey what a call returns; it conveys provenance and caveats but not the shape of results or how the seven filters and cursor behave. For a read-only list tool whose annotations cover the safety profile, this is adequate but leaves real gaps around parameters and return values.

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?

All seven parameters (after, limit, family, league, status, event_id, market_id) have 0% schema description coverage, so the description carries the full burden — and it says nothing about any of them. Terms like 'futures selections' hint at family/league scoping but give no meaning, format, or interaction rules for the filters or the 'after' cursor.

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 gives a specific verb and resource ('Read stored FanDuel futures selections and prices') and scopes it to a single book and a stored snapshot, which separates it from live or multi-book odds tools. It does not name a sibling explicitly, so an agent must infer the boundary from the word 'stored' and 'FanDuel'.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: 'stored' plus 'no live freshness guarantee' signals this is for historical/captured futures data, not live pricing, and 'no cross-book matching' tells the agent not to use it for line comparison. No alternative tool is named and there is no explicit when-not statement.

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.