Crawlora MCP

yahoo_sports_team

Read-only

Fetch Yahoo Sports details for one team identifier. Use yahoo_sports_team_roster for the team's player roster.

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

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."New value: +"Required. Yahoo league key from yahoo-sports-leagues."

First observedOct 5, 2026

TDQS

A3.6/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 safety and world-access traits are covered. The description adds almost nothing beyond the annotations -- no mention of data freshness, whether results are cached, or what kind of team data (stats/records/metadata) is returned, though an output schema exists to cover returns. Adequate but thin for a tool with annotations carrying the load.

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 short sentences, no waste, with the disambiguation routed up front. Front-loading is good; nothing superfluous is present.

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?

With an output schema, full param coverage, and read-only annotations, the agent has what it needs. The only gap is the vagueness of 'details,' but given the supporting structured fields this is nearly complete.

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' (with slug examples) and 'league' (pointer to yahoo-sports-leagues) are fully documented in the schema. The description adds no parameter meaning beyond that, so the baseline 3 is correct.

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 ('Fetch') and resource ('Yahoo Sports details for one team identifier'), and names the roster sibling as distinct. The word 'details' is somewhat generic about what data is returned, but the operation is clearly identifiable.

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 routes the agent to yahoo_sports_team_roster for the player roster, which is a genuine alternative selector. It gives no guidance on when NOT to use this tool (e.g. schedule vs team), but the one alternative is handled well.

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?