Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_player

Fetch an MLB player's profile by numeric ID, returning name, position, team, bats/throws, birth details, age, height, weight, jersey number, and debut date. Unknown IDs return 404.

Instructions

Get an MLB player. Returns an MLB player by numeric id. The response has the full name, position, bats and throws sides, birth date, city and country, current age, height, weight, jersey number, MLB debut date, active flag and current team. Unknown players return 404.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric MLB player id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.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 does disclose the error path ('Unknown players return `404`') and enumerates the response payload, which is real added value. It omits other behavior an agent would want, such as whether the `id` is an MLBAM id, where to obtain it, or any caching/auth/rate-limit characteristics.

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?

The verb+resource leads the first sentence, and the follow-on sentences earn their space by enumerating the return payload and the 404 behavior – valuable given there is no output schema. The field list is long but defensible; it is not padded with filler.

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?

Since no output schema exists, the description's field enumeration (name, position, bats/throws, birth data, age, height, weight, jersey, debut, active flag, team) plus the 404 case makes the contract reasonably complete for a single-parameter lookup. The remaining gap is how an agent obtains a valid numeric id, which matters in a catalog full of search-style siblings.

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 sole `id` parameter is already documented in the schema as 'Numeric MLB player id'. The description only echoes that same fact ('by numeric `id`') without adding format, range, or source details, so the baseline 3 for a fully-covered single-parameter schema 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?

The description states a specific verb and resource ('Get an MLB player ... by numeric `id`') and previews the returned fields, so an agent knows exactly what this resource is. It does not, however, name or contrast any sibling such as mlb_player_stats or mlb_search, leaving the boundary between this tool and the other MLB player tools to inference.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance or mention of alternatives; the description never says whether a name-based search (e.g. mlb_search) is needed first to obtain the numeric id. The only usable hint is that the lookup is keyed by a numeric id, which implies a prior resolution step but never states it.

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