MLB Stats MCP

Overview Schema Source Related Servers Discussions Admin

get_schedule

Read-onlyIdempotent

Retrieve MLB games, scores, and probable pitchers for a specific date or short date range, with optional team filtering by name, abbreviation, or ID.

Instructions

Get MLB games (with scores and probable pitchers) for a date or date range.

Args:
    date: Date as YYYY-MM-DD; defaults to today (US Eastern).
    end_date: Optional end of range (YYYY-MM-DD). Keep ranges short (a few weeks at most).
    team: Optional team filter: name, abbreviation or id.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_schedule"
  }
}

Input Schema

Name	Required	Description	Default
`date`	No
`team`	No
`end_date`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and open-world behavior, so the safety profile is covered. The description adds value beyond that by disclosing what the response contains (scores, probable pitchers) and the timezone basis of the default date, though it says nothing about pagination, rate limits, or behavior for out-of-season/empty ranges.

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

Conciseness4/5

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

The summary sentence is front-loaded and the Args block is terse, with every line carrying information an agent needs. The Args-style formatting is slightly mechanical but not wasteful; no sentence is redundant.

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?

For a three-parameter read-only list tool with an output schema already present, the description covers everything needed to invoke correctly: formats, defaults, timezone, filtering options, and a range-size guardrail. Return-value detail is unnecessary given the output schema, and the brief mention of scores/pitchers is a bonus rather than a gap-filler.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry all parameter meaning -- and it does. Each of the three parameters is documented with format (YYYY-MM-DD), defaults (today, US Eastern), optionality, accepted team identifier forms (name, abbreviation, or id), and a practical constraint on range length for end_date.

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 ('Get MLB games') with the scope ('for a date or date range') and even previews the payload ('with scores and probable pitchers'). The plural, date-range framing implicitly separates it from the single-game sibling get_game, but no sibling is named explicitly, which keeps it one notch below a 5.

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?

It supplies real operating context: the date defaults to today in US Eastern, the range is optional, and ranges should be kept to a few weeks at most. What's missing is explicit routing guidance -- e.g., when to use this versus get_game for a single game or get_standings for records.

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

Deploy Server