Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_sports_odds_games

Fetch current Yahoo Sports game IDs for a specified odds league to map games into odds workflows. Returns an empty games array when the league is off-season.

Instructions

Yahoo Sports current game IDs for an odds league. Returns the current games and their Yahoo game IDs from the public Graphite leagueGameIds operation. A valid current league can return an empty games array during its off-season. Use the sportsbook catalog for the complete league value space.

Input Schema

NameRequiredDescriptionDefault
leagueYesExact Graphite league value from yahoo-sports-sportsbook-catalog

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses that this is a public read-only fetch, identifies the source operation, and calls out the notable edge case that an in-season-valid league can legitimately return an empty games array. It stops short of documenting pagination, rate limits, or the exact response shape, which keeps it out of the top score.

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?

The opening sentence front-loads the resource and each subsequent sentence adds a distinct fact (source operation, off-season empty result, league catalog). Mild redundancy between the first sentence and the 'Returns the current games...' sentence keeps it from being maximally tight.

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 one-parameter, no-annotation, no-output-schema tool, the description covers purpose, the source of truth for the parameter, and the main surprising return condition. An agent has enough to call it correctly, though the absence of output schema means the exact fields returned are only loosely sketched.

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?

Schema description coverage is 100% and the single league parameter is a fully enumerated field already described as the exact Graphite league value. The description's pointer to the sportsbook catalog for the broader league value space adds a little navigational value but largely restates what the schema already says.

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 states a specific verb and resource: it returns the current games and their Yahoo game IDs for a given odds league, and names the underlying Graphite leagueGameIds operation. It is clear what data comes back, though it does not explicitly distinguish itself from the sibling yahoo_sports_odds_game (single-game odds) or yahoo_sports_odds_featured/trending, so an agent must infer the split from the name.

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?

It gives one useful routing hint — use yahoo-sports-sportsbook-catalog for the complete league value space — and warns that a valid league can return an empty array during the off-season. However, it never says when to pick this tool over yahoo_sports_odds_game or the featured/trending odds siblings, so the choice of tool is left implicit.

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