Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_sports_golf_player

Retrieve a golfer’s Yahoo Sports profile, current-season stats, and tournament-by-tournament history by supplying the canonical player URL.

Instructions

Yahoo Sports golf player profile. Returns one golfer's profile, current-season stats, and tournament-by-tournament history from Yahoo's public player page. Supply the canonical player URL from golf-players or another Yahoo golf response.

Input Schema

NameRequiredDescriptionDefault
player_urlYesCanonical Yahoo Golf player profile URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully identifies the operation as reading a public Yahoo player page and enumerates the return categories, but it does not cover failure behavior, pagination, freshness, or URL validation.

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?

Three short sentences with the resource, return contents, and input source front-loaded. Every sentence contributes useful information without repetition.

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?

This is a low-complexity, single-parameter tool with full schema coverage and no annotations. The description explains the returned data and how to obtain the required URL, making it complete enough to call correctly, though it could mention freshness or failure conditions.

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%, so the schema already documents the single parameter. The description adds provenance beyond the schema by specifying that the canonical URL should come from golf-players or another Yahoo golf response.

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 resource and return set: one golfer's profile, current-season stats, and tournament-by-tournament history. It also differentiates this single-entity tool from the list-oriented sibling by telling the agent to supply a canonical URL from 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?

It clearly explains the prerequisite source for the required player_url, naming golf-players or another Yahoo golf response. It does not give explicit when-not guidance, but the intended usage sequence is obvious.

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

Deploy Server

Other Tools