Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

yahoo_sports_golf_player

Read-only

Fetch one golfer's public profile, biography, season statistics, and tournament history by canonical player_url from yahoo_sports_golf_players.

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": {
      "player_url": "<player_url>"
    },
    "name": "yahoo_sports_golf_player"
  }
}

Input Schema

NameRequiredDescriptionDefault
player_urlYesRequired. Full Yahoo Golf player URL from a directory entry, e.g. https://sports.yahoo.com/golf/players/Ludvig+Aberg/22880/.

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. Added

TDQS

A4.2/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 that the response spans profile/bio/stats/history, but says nothing about result size, season scoping, or what happens with a stale/invalid player_url.

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?

A single sentence that front-loads the verb, the entity, and the payload, then closes with the input provenance. No redundant or filler text.

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?

An output schema exists and the single parameter is fully documented in both schema and description, so an agent has everything needed to invoke it correctly. The only gap is sibling disambiguation against yahoo_sports_golf_player_news and yahoo_sports_player.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and includes a worked URL example, so the baseline is 3. The description adds real value by constraining the value to a 'canonical player_url' sourced from the directory tool, warning the agent away from arbitrary or constructed URLs.

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?

States a specific verb and resource ('Fetch one golfer's public profile') and enumerates the payload (biography, season statistics, tournament history), so an agent knows exactly what comes back and can distinguish it from directory-style siblings like yahoo_sports_golf_players.

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 says the input must come 'from yahoo_sports_golf_players', which routes the agent to the prerequisite directory tool. It does not address when to prefer yahoo_sports_golf_player_news instead, so no explicit exclusion is given.

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