Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

yahoo_sports_standings

Read-only

Fetch Yahoo Sports league standings table rows grouped by conference or division. Use espn_standings or mlb_standings when you specifically need those providers' standings.

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>"
    },
    "name": "yahoo_sports_standings"
  }
}

Input Schema

NameRequiredDescriptionDefault
leagueYesRequired. Yahoo league key with standings=true in yahoo-sports-leagues.
seasonNoOptional soccer season year from yahoo-sports-soccer-scoreboard. Omit to use Yahoo's current season.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / league / description
      Previous value: -"Required. League key. One of nfl, nba, wnba, mlb, nhl."New value: +"Required. Yahoo league key with standings=true in yahoo-sports-leagues."
    • addedInput schema / properties / season
      Added value: +{
+  "description": "Optional soccer season year from yahoo-sports-soccer-scoreboard. Omit to use Yahoo's current season.",
+  "type": "integer"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior3/5

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

The annotations already declare this as a read-only, open-world operation, so the safety profile is covered. The description adds useful output context by noting that standings are grouped by conference or division, but it does not describe freshness, pagination, or other operational traits an agent might care about.

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?

The description is two sentences with no wasted text. The primary purpose is front-loaded, and the alternative-provider routing is placed immediately after it.

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 low-complexity read-only standings fetch with rich schema coverage, annotations, and an output schema, the description is complete enough. An agent can understand the source, output grouping, and when to choose sibling standings tools without needing more from the description.

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 the schema already explains the required league key and optional season parameter in detail. The description does not add parameter-specific guidance beyond what the schema provides, making a baseline 3 appropriate.

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?

The description states a specific verb and resource: fetching Yahoo Sports league standings table rows. It also identifies the grouping by conference or division, which distinguishes it from generic standings tools and makes the scope of the result clear.

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

Usage Guidelines5/5

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

It explicitly routes the agent to espn_standings or mlb_standings when those providers' standings are specifically needed. That gives a clear alternative condition for selecting this Yahoo-specific tool rather than leaving provider choice to inference.

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

All Crawlora MCP toolsInspect
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