Skip to main content
Glama

FastballAPI

Pitch mix

get_pitch_mix
Read-onlyIdempotent

Use for a pitcher's arsenal in a season: each pitch type's usage, average and top velocity, whiff rate per swing and ball rate. Velocities come from whole-mph readings cut down rather than rounded, so the averages run about half a mile per hour under Statcast's. Costs 5 credits.

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": {
      "pitcher_id": "<pitcher_id>"
    },
    "name": "get_pitch_mix"
  }
}

Input Schema

NameRequiredDescriptionDefault
seasonNoSeason (a year; default: the latest; ignored with game_id).
pitcher_idYesPlayer id.
season_typeNoregular, postseason, or all (default): which games' pitches.

Output Schema

NameRequiredDescriptionDefault
mixYes
noteNo
countYes
seasonYes
pitcherYes
pitchesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / season_type
      Added value: +{
      +  "description": "regular, postseason, or all (default): which games' pitches.",
      +  "enum": [
      +    "regular",
      +    "postseason",
      +    "all"
      +  ],
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / pitcher_id / description
      Previous value: -"ESPN athlete id."New value: +"Player id."
  3. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious context on top: the velocity figures are truncated whole-mph readings that run roughly half a mph below Statcast, which prevents a wrong cross-source comparison, plus a 5-credit cost that lets an agent budget calls.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences with the use case front-loaded and no filler, which is good structure. However, the opening is a run-on inventory of five metrics before any behavioral caveat, and the cost note is tacked on at the end rather than surfaced where an agent planning calls would look.

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?

An output schema exists, so return values need no explanation, and the description covers scope, data provenance and cost for a modest three-parameter read tool. Minor gaps remain: no note on how much history or which seasons are covered, and no hint about how pitcher_id relates to search_players.

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%, so pitcher_id, season and season_type are already documented, including the default and the enum values. The description only echoes the season scoping ("in a season") and adds no format or edge-case detail beyond the schema, so baseline 3 applies.

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 names a concrete resource (a pitcher's arsenal for a season) and enumerates the returned measures: usage, average and top velocity, whiff rate per swing, ball rate. That field-level specificity makes it distinguishable from raw-pitch siblings like get_pitches or get_plate_appearances without opening either schema.

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?

"Use for a pitcher's arsenal in a season" is an explicit positive usage cue scoped to one pitcher and one season, which sets expectations against game-level or league-level tools. It stops short of naming an alternative or stating when not to use it, so the routing guidance is clear but not exhaustive.

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.