SiteCheck Agent Intel & Dev

MLB games for one date from the official MLB Stats API

dev_mlb_statsapi

Read-only

MLB games for one date from the official MLB Stats API: teams, scores, status, venue and current inning. Regular and postseason games as the schedule lists them; the date is the schedule date (UTC game times). MLB copyright applies. Related tools on this server, for a different need: dev_mlb_stats when you need MLB player season stats and bio from the official MLB Stats; dev_espn_mlb_scoreboard when you need ESPN MLB scoreboard for one date: every game with away. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": "dev_mlb_statsapi"
  }
}

Input Schema

Name	Required	Description	Default
`date`	No	Schedule date YYYY-MM-DD (default: yesterday UTC)

Output Schema

Name	Required	Description	Default
`date`	No
`count`	No
`games`	No
`source`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnlyHint, openWorldHint), and the description adds material behavior beyond them: coverage of regular and postseason games, that the date is the schedule date with UTC game times, an MLB copyright notice, and an explicit paid-call model ($0.002 USDC via x402 on Base/Solana/Arc) with failed calls uncharged. That price and failure-charging disclosure is exactly the kind of context an agent cannot get from structured fields.

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?

Purpose and returned fields are front-loaded, followed by scoping, then sibling routing and pricing, which is a sensible order. The pricing clause is long and the ESPN sibling clause trails off mid-thought ('every game with away'), leaving a slightly malformed sentence that should have been tightened or completed.

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?

An output schema exists, so return values need not be spelled out, and annotations cover safety. Given a one-parameter, read-only tool, the definition supplies everything still missing: coverage window, date semantics, cost, and sibling alternatives.

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

Parameters4/5

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

Schema coverage is 100% and the date parameter already documents the YYYY-MM-DD format and yesterday-UTC default, so the baseline is 3. The description adds genuine meaning by clarifying that the date is the schedule date and that game times are UTC, which resolves ambiguity the schema alone leaves open.

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+resource+scope (MLB games for one date from the official MLB Stats API) and enumerates the returned fields (teams, scores, status, venue, current inning). It also names the two most likely confusable siblings and what each covers, so an agent can separate this from dev_mlb_stats and dev_espn_mlb_scoreboard without opening a schema.

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 explicit routing rules for the alternatives: dev_mlb_stats for player season stats and bio, dev_espn_mlb_scoreboard for ESPN's one-date scoreboard. It also implicitly scopes this tool to schedule-derived game lists, so the when-to-use decision is fully determined.

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

All SiteCheck Agent Intel & Dev tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?