MLB Stats MCP

Overview Schema Source Related Servers Discussions Admin

search_players

Read-onlyIdempotent

Find MLB players by full or partial name and return their player_id for use with other player tools. Optionally limit results to active players.

Instructions

Find MLB players by name and return their player_id (needed by other player tools).

Args:
    name: Full or partial name, e.g. "Ohtani" or "Aaron Judge".
    active_only: Only return currently active 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": {
      "name": "<name>"
    },
    "name": "search_players"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`active_only`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 14, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds meaningful semantics: matching is by full or partial name and active_only restricts to current players. However, it says nothing about result-set size limits or how ambiguous partial matches (e.g. "Aaron") are handled, which is the main behavioral unknown for a search tool.

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?

Two lines: a front-loaded purpose sentence followed by a compact Args block. Every sentence carries information and there is no filler or redundancy.

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?

For a simple two-parameter lookup with an output schema present, the definition covers purpose, both parameters, and the intended call sequence. The only unaddressed item is result-count/pagination behavior, which is a modest gap rather than a blocker.

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 description coverage is 0%, so the description must carry the parameter burden, and it does: name is defined as full or partial with concrete examples, and active_only as returning only currently active players. Minor gap: no guidance on minimum match length or expected cardinality of results for broad queries.

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 concrete verb and resource ("Find MLB players by name") plus the returned key ("player_id") and its downstream purpose ("needed by other player tools"). That return-value framing cleanly separates it from siblings like get_player_info or get_player_stats that consume a player_id.

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?

Implies the correct usage context: call this first to resolve a name into a player_id before using other player tools. It does not explicitly state when not to use it or name an alternative when a player_id is already known, so guidance is clear but not complete.

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

Deploy Server