Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_game

Retrieve an MLB game feed by numeric ID to get status, teams, records, score, inning-by-inning runs, probable pitchers, and box-score totals. Use for summaries, not full play-by-play.

Instructions

Get an MLB game feed. Returns an MLB game summary by numeric id. The response has the status, both teams with records and score, inning-by-inning runs, probable pitchers, winning, losing and save pitchers, and team box-score totals. It does not include the full play-by-play. Use the play-by-play endpoint for that.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric MLB game id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It thoroughly discloses the response contents (status, teams, records, score, inning runs, pitchers, box-score totals) and what is excluded, but does not mention error behavior for invalid ids or any rate/caching constraints. For a read-only lookup this is strong but not complete.

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?

The description is front-loaded with the core action, then adds return detail and a crucial exclusion. Every sentence earns its place, with no redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description fully describes the return payload, and with no annotations it implies a safe read operation. Nothing needed to call this simple lookup correctly is missing.

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 description adds no meaning beyond the schema: it says 'by numeric `id`', which matches the schema's 'Numeric MLB game id'. Baseline 3 is appropriate when the schema already documents the only parameter.

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 states a specific verb and resource ('Get an MLB game feed') and what it returns ('an MLB game summary by numeric `id`'). It explicitly distinguishes itself from the play-by-play sibling, so an agent can tell what this tool provides without inspecting schemas.

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

Usage Guidelines5/5

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

It gives an explicit exclusion and alternative: 'It does not include the full play-by-play. Use the play-by-play endpoint for that.' This tells the agent when not to use this tool and where to go instead, satisfying the highest bar for usage guidance.

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