Crawlora MCP

yahoo_sports_team_schedule

Read-only

Fetch scheduled game results for one Yahoo Sports team identifier. Use yahoo_sports_scoreboard for a league-wide game board.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "league": "<league>",
      "team": "<team>"
    },
    "name": "yahoo_sports_team_schedule"
  }
}

Input Schema

Name	Required	Description	Default
`team`	Yes	Required. Yahoo Sports team slug, e.g. green-bay, la-lakers, boston.
`league`	Yes	Required. Yahoo league key from yahoo-sports-leagues.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 1, 2026

changedInput schema / properties / league / description

Previous value: -"Required. League key. One of nfl, nba, wnba, mlb, nhl, college-football."New value: +"Required. Yahoo league key from yahoo-sports-leagues."

First observedOct 5, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only the single-team scope, and says nothing about which season/time window is returned (there is no season parameter) or how results are ordered -- meaningful gaps for a schedule tool, though the existing output schema reduces the burden.

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?

Two sentences, zero waste: the scope statement is front-loaded and the sibling routing follows immediately. Nothing could be removed without losing information.

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

Completeness5/5

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

For a two-param read tool with full schema coverage, an output schema, and annotations covering safety and openness, the definition supplies what's needed to call it correctly. The only unstated item is the default time window, which is a minor gap against otherwise rich structured metadata.

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%, so both `team` (slug example) and `league` (key from yahoo-sports-leagues) are already fully documented, making 3 the baseline. The description's 'one Yahoo Sports team identifier' merely restates the team parameter and adds no format or constraint detail beyond the schema.

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 ('Fetch scheduled game results') scoped to 'one Yahoo Sports team identifier', and explicitly contrasts with the league-wide board. Slightly blurred by combining 'scheduled' with 'results', but an agent can distinguish it from yahoo_sports_scoreboard without opening the 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?

Gives clear routing guidance: use yahoo_sports_scoreboard for a league-wide board. However it omits the arguably closer sibling yahoo_sports_league_schedule, which is not mentioned, so the team-vs-league-vs-catalog choice is only partially disambiguated.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?