Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_sports_player_search

Search Yahoo Sports player pages across NFL, NBA, MLB, and golf by name or prefix of at least three characters to find matching players and league-specific results.

Instructions

Yahoo Sports player search. Searches Yahoo's public playerSearch operation, as used by the NFL, NBA, MLB, and Golf player pages. Yahoo requires at least three characters and currently hard-codes onActiveRosterOnly=false in these search boxes.

Input Schema

NameRequiredDescriptionDefault
nameYesPlayer name or prefix (at least three characters)
leagueYesPlayer-search page key

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose one genuinely useful behavioral fact not in the schema: onActiveRosterOnly is hard-coded to false, implying results include players off the active roster. It says nothing about result shape, ranking, or result limits, which is a gap for a search tool with zero annotation coverage.

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?

Three short sentences, front-loaded with what the tool is before the operational caveats. Minor waste: the three-character requirement is restated from the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

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

Adequate for a simple two-parameter search with no output schema, and the roster caveat is a nice touch, but an agent still does not know what a result contains or how many results come back. That leaves it at minimum viable rather than complete.

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 both parameters are documented there, including the three-character rule and the league enum, so the description adds little parameter meaning beyond "player name or prefix" already implied. Baseline 3 is appropriate.

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 and resource ("player search" against Yahoo's public playerSearch operation) and names the four league pages it backs. This separates it from detail-oriented siblings like yahoo_sports_player or yahoo_sports_golf_players, though it never explicitly contrasts with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an implicit usage context (the search boxes on NFL/NBA/MLB/Golf player pages) and the three-character minimum, but there is no statement of when to pick this over yahoo_sports_player or yahoo_sports_team_roster, and no exclusions.

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