Skip to main content
Glama

FastballAPI

Game

get_game
Read-onlyIdempotent

Use for one game in full: line score, every batter's and pitcher's line, each sportsbook's opening and closing line, and the win-probability range. For every plate appearance use get_plate_appearances. Costs 5 credits. Prices are market information; no tool places, accepts or tracks wagers.

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": {
      "game_id": "<game_id>"
    },
    "name": "get_game"
  }
}

Input Schema

NameRequiredDescriptionDefault
leagueNoLeague. Defaults to mlb. One of: mlb, ncaabase.
game_idYesGame id, from get_games or get_schedule.

Output Schema

NameRequiredDescriptionDefault
gameYes
oddsYes
battingYes
pitchingYes
win_probabilityYes
plate_appearancesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / game_id / description
      Previous value: -"ESPN game id, from get_games or get_schedule."New value: +"Game id, from get_games or get_schedule."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, so the safety profile is covered. The description adds two things annotations cannot: a concrete cost (5 credits) and a scope disclaimer that no tool places, accepts or tracks wagers — valuable for an agent reasoning about what this data can be used for. Auth requirements and rate limits are not mentioned.

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?

Three short sentences with zero filler: scope first, routing second, cost and legal/scope caveat last. Front-loaded and every sentence carries distinct 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?

With an output schema present, the description is not obliged to explain return values, and it still summarizes them. Cost, the sibling handoff and the no-wagering caveat make it close to complete; only permission/auth behavior is unaddressed.

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 in the schema, including the league enum and that game_id comes from get_games or get_schedule. The description adds no parameter-level detail beyond implying a single game, so the 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 specific resource and enumerates the payload concretely: line score, every batter's and pitcher's line, each sportsbook's opening and closing line, and win-probability range. It explicitly distinguishes itself from get_plate_appearances, so an agent can choose between the two 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 one game in full" plus the explicit handoff to get_plate_appearances covers the main selection decision cleanly. It stops short of addressing other plausible alternatives (e.g. odds-only or line-movement siblings), so it is clear context without full exclusion guidance.

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.