Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_schedule

Fetch MLB game schedules and scores for a date or date range, optionally filtered by team, including status, probable pitchers, venue, and series info.

Instructions

Get the MLB schedule and scores. Returns MLB games, teams, scores, status, probable pitchers, venue, and series information for one date or date range, optionally filtered to a team.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoSingle date in YYYY-MM-DD format
team_idNoNumeric MLB team id
end_dateNoRange end in YYYY-MM-DD format
game_typeNoGame type
start_dateNoRange start in YYYY-MM-DD format

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.7
    • addedInput schema / properties / game_type
      Added value: +{
+  "description": "Game type",
+  "enum": [
+    "S",
+    "R",
+    "F",
+    "D",
+    "L",
+    "W",
+    "C",
+    "P",
+    "A",
+    "I",
+    "E"
+  ],
+  "type": "string"
+}
  2. Added

TDQS

A3.5/5.0
Behavior3/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 usefully discloses the returned content (games, teams, scores, status, probable pitchers, venue, series), which signals a read-only lookup, but it does not state pagination behavior, rate limits, or that it is non-mutating. Reasonable but incomplete for a zero-annotation tool.

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?

Two sentences, front-loaded with the core purpose followed by the return contents and scoping options. No filler or repetition. Slightly dense in the second sentence but every clause carries 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?

There is no output schema, so the description correctly compensates by enumerating the return fields. With all five params documented in the schema, the main gap is the unexplained game_type enum semantics and the date vs. start_date/end_date distinction, which the description could have clarified.

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 the schema already documents date, start_date, end_date, team_id, and game_type. The description only restates that date/date-range and team filtering are supported, adding no syntax or behavioral detail beyond the schema. Baseline 3 applies.

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 gives a specific verb and resource ("Get the MLB schedule and scores") and enumerates the return payload, so the agent knows exactly what the tool produces. It does not, however, differentiate itself from close siblings like mlb_game, mlb_game_boxscore, or mlb_standings, so an agent must infer the boundary.

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

Usage Guidelines3/5

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

It states the operative context ("for one date or date range, optionally filtered to a team"), which implies when the tool is appropriate. But there is no explicit when-to-use/when-not guidance and no naming of alternatives such as mlb_game for single-game detail, leaving the routing decision to inference.

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