Skip to main content
Glama
lacausecrypto

Sports Hub MCP Server

by lacausecrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

mlb: Get schedule

mlb_get_schedule
Read-onlyIdempotent

Retrieve MLB game schedules by date or date range with teams, scores, and status. Filter results by team or league level.

Instructions

Get the MLB game schedule for a date or date range. Returns games with scores, status, and teams.

Input Schema

NameRequiredDescriptionDefault
dateNoSingle date in YYYY-MM-DD format (e.g. 2024-04-15)
fieldsNoKeys to keep (comma-separated).
teamIdNoFilter by team ID
endDateNoRange end date YYYY-MM-DD
sportIdNoSport ID (1=MLB, 11=AAA, 12=AA, 13=A, 14=A-short)
startDateNoRange start date YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / fields
      Added value: +{
+  "description": "Keys to keep (comma-separated).",
+  "type": "string"
+}
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety and idempotency are covered. The description adds genuinely useful context beyond that by disclosing the return contents ('games with scores, status, and teams'), which matters given there is no output schema.

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?

Two tightly written sentences with the primary purpose front-loaded and the return summary second. No filler or repetition.

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?

For a read-only schedule tool whose safety traits are already in annotations and whose parameters are fully covered by the schema, the description covers what the tool does and what it returns. It could be stronger by noting single-game alternatives, but nothing essential for invoking it 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%, so the schema already documents every parameter including the date/range fields, teamId, sportId enum-like values, and fields projection. The description mentions 'date or date range' but adds no format or usage detail beyond what the schema provides, so the baseline of 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?

States a specific verb and resource ('Get the MLB game schedule') plus scope ('for a date or date range'), which an agent can act on directly. It does not explicitly distinguish itself from the sibling mlb_get_game (single game) or other league schedule tools, so sibling differentiation is left implicit.

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?

Usage is implied by the naming and the date/range framing, but there is no explicit when-to-use / when-not guidance and no mention of alternatives such as mlb_get_game for a single matchup. The agent must infer context from the tool name and sibling list.

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