Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_sports_odds_game

Fetch available moneyline, spread, and over/under markets and selections for a single Yahoo Sports game by game ID, enabling quick odds lookup.

Instructions

Yahoo Sports game odds markets. Returns the available moneyline, spread and over/under markets and selections for one game using Yahoo's public Graphite playbookGame operation. Get game_id from yahoo-sports-odds-games, yahoo-sports-odds-trending, or yahoo-sports-odds-featured.

Input Schema

NameRequiredDescriptionDefault
tzNoOptional IANA timezone for game time display; defaults to UTC
game_idYesYahoo game ID from an odds game list

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the data source ('Yahoo's public Graphite playbookGame operation') and the shape of the payload (markets plus selections), which is useful given there's no output schema. It says nothing about empty-market cases, stale/live odds, or whether calls are rate limited, so it is adequate rather than rich.

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

Conciseness5/5

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

Three short sentences: what it returns, what backs it, and how to get the required ID. Nothing is redundant and the payload description is front-loaded ahead of the prerequisite.

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

Completeness4/5

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

For a two-parameter read tool with no output schema, the description covers purpose, returned content and ID provenance. The remaining gap is mild: it does not state whether prices/lines are included in the selections or how a game with no posted markets is represented.

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

Parameters4/5

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

Schema coverage is 100%, so both tz and game_id are already documented, establishing a baseline of 3. The description adds value beyond the schema by stating that game_id must be obtained from the odds game-list/trending/featured tools, which is provenance the schema does not supply.

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

Purpose5/5

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

States a specific verb and resource: returns moneyline, spread and over/under markets and selections for one game. The scoping ('for one game') and the enumerated market types let an agent distinguish this from the sibling list tools yahoo_sports_odds_games, yahoo_sports_odds_trending and yahoo_sports_odds_featured without opening any schema.

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

Usage Guidelines4/5

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

Explicitly tells the agent where the required game_id comes from by naming three sibling tools, which is the key prerequisite for calling this one. It stops short of stating when not to use it (e.g. to browse many games, use yahoo_sports_odds_games), but the precondition guidance is strong.

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

Deploy Server

Other Tools