Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

yahoo_sports_team_roster

Read-only

Fetch the roster for one Yahoo Sports team identifier. Use yahoo_sports_team for team details and metadata.

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

Input Schema

NameRequiredDescriptionDefault
teamYesRequired. Yahoo Sports team slug, e.g. green-bay, la-lakers, boston.
leagueYesRequired. Yahoo league key from yahoo-sports-leagues.

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. Changed1 schema field changed
    • 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."
  2. First observed

TDQS

A4/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 and external-data profile is covered. The description adds no further behavioral detail such as whether a roster is a snapshot for the current season, how large the payload is, or how missing/invalid team slugs behave. An output schema exists, so return-shape disclosure is not required, but the description still adds little beyond the annotations.

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 short sentences, zero filler, with the action front-loaded and the sibling routing placed immediately after. Every sentence earns its place.

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 present, a read-only annotation set, and fully documented parameters, the definition supplies what an agent needs to select and call the tool. The only gap is that it never mentions the required league scoping in prose, so an agent skimming the description alone would not know two parameters are mandatory.

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%, with both `team` (slug examples) and `league` (league key from yahoo-sports-leagues) documented in the schema itself. The description only hints that a single team identifier is expected and says nothing about the league parameter or their combination. Baseline 3 is appropriate since the schema does the heavy lifting.

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 ("Fetch the roster for one Yahoo Sports team identifier") and explicitly distinguishes itself from the sibling yahoo_sports_team, which is designated for team details and metadata. An agent can tell the two apart without opening either 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?

It names the alternative (yahoo_sports_team) and the condition that selects it (team details/metadata), which gives clear routing context for the most likely confusion. It does not state exclusions or prerequisites for this tool itself, so it falls short of a full when/when-not treatment.

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