Crawlora MCP

yahoo_sports_player_search

Read-only

Search Yahoo Sports public player records by supported league and a name prefix of at least three characters. Use yahoo_sports_leagues to discover league keys.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	Required. Search text; Yahoo's UI starts searching at three characters.
`league`	Yes	Required. Yahoo player-search page key: nfl, nba, mlb, or golf.

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.

AddedOct 31, 2026

TDQS

A3.8/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 scope are covered. The description adds only that records are 'public' and repeats the three-character prefix rule already implied by the schema; it says nothing about result volume, ranking, or empty-result behavior.

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 filler, with the search scope front-loaded and the prerequisite hint second. 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.

Completeness4/5

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

A read-only, two-parameter search tool with full schema coverage, an output schema, and annotations carrying the safety profile — the description plus structured data is sufficient to call it correctly. Only the sibling disambiguation is notably absent.

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 schema already enumerates the league keys (nfl, nba, mlb, golf) and explains the three-character search behavior. The description's league-key discovery hint is useful routing advice but adds no new parameter-level meaning, so the baseline of 3 applies.

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 (Search) and resource (Yahoo Sports public player records) plus the scoping constraint of league + name-prefix. It does not explicitly contrast with the nearby siblings yahoo_sports_player / yahoo_sports_golf_players, so an agent could not fully rule those out from the description alone.

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 a concrete prerequisite workflow: use yahoo_sports_leagues to discover league keys before calling. It sets clear context for when the tool applies but offers no exclusions or guidance on when a different player tool is preferable.

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?