Skip to main content
Glama

FastballAPI

Search players

search_players
Read-onlyIdempotent

Use to find a player's id by name (partial names work). Costs 1 credit.

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

NameRequiredDescriptionDefault
nameYesFull or partial name.
limitNo
leagueNoLeague. Defaults to mlb. One of: mlb, ncaabase.

Output Schema

NameRequiredDescriptionDefault
noteNo
countYes
playersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / note
      Added value: +{
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description clears the lower bar. It adds genuinely useful context beyond them: the call costs 1 credit and partial names are accepted, both of which affect whether and how an agent invokes it. It does not discuss what happens when many players match, but the output schema can carry that.

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 short sentences, zero waste, and the primary use case is front-loaded before the cost note. Nothing could be removed without losing information.

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 three-parameter read-only search with an output schema and full annotation coverage, the description supplies the essentials: purpose, partial matching, and cost. The only meaningful gap is behavior on multiple matches / how limit interacts with a fuzzy name search.

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 67% and the name field already documents "Full or partial name," so the description's note about partial names largely restates the schema. It adds nothing about the limit parameter or when to set league, leaving those to the enum and min/max constraints.

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 — find a player's id by name — and notes that partial names work, which distinguishes it from get_player, which presumably needs an id. It stops short of naming get_player as the follow-up step, but an agent can still tell the two apart.

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?

"Use to find a player's id by name" implies the entry point for a name-based lookup, but there is no explicit when-not guidance, no mention of get_player as the follow-up, and no explanation of when to apply the league filter versus searching across leagues.

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.