Skip to main content
Glama

Crawlora MCP

yahoo_sports_golf_leaderboard

Read-only

Fetch the Yahoo Sports golf tournament leaderboard with ranks, scores to par, status, and round strokes. Use yahoo_sports_golf_schedule to find tournament dates and events.

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": {
      "tournament": "<tournament>"
    },
    "name": "yahoo_sports_golf_leaderboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
seasonNoOptional. 4-digit season year (a tournament id is reused across years). Defaults to the tournament's most recent season.
tournamentYesRequired. Yahoo Sports golf tournament id from a golf-schedule response's id field, e.g. golf.e.23.

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. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, and an output schema exists, so the enumeration of returned fields in the description is largely redundant. No additional behavioral context (rate limits, auth, data freshness) is supplied.

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 sentences, front-loaded with the action and returned data, with the routing hint second. No filler, though slightly redundant with the output schema.

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 annotations covering safety, a fully documented 2-param schema, and an output schema for return values, the short description is sufficient for correct invocation. Only minor routing context is missing.

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 coverage is 100% and the schema already documents both 'season' and 'tournament', including the golf.e.23 id format. The description adds no syntax or format detail beyond what the schema provides, so baseline 3 applies.

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 (Fetch) and resource (Yahoo Sports golf tournament leaderboard) and enumerates the data returned (ranks, scores to par, status, round strokes). An agent can distinguish it from the schedule sibling at a glance.

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 a concrete alternative (yahoo_sports_golf_schedule) for finding tournament dates and events, which is the key routing decision for this family. It stops short of stating explicit when-not conditions, but the context is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources