Skip to main content
Glama
lacausecrypto

Sports Hub MCP Server

mlb_get_schedule

Retrieve MLB game schedules and scores for specific dates or date ranges, including team details and game status.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoSingle date in YYYY-MM-DD format (e.g. 2024-04-15)
startDateNoRange start date YYYY-MM-DD
endDateNoRange end date YYYY-MM-DD
teamIdNoFilter by team ID
sportIdNoSport ID (1=MLB, 11=AAA, 12=AA, 13=A, 14=A-short)
Behavior3/5

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

With no annotations, description must disclose behaviors. It states this is a read operation returning schedule data, but omits details like authentication requirements, rate limits, or whether only published games are returned. Acceptable for a simple read tool but not thorough.

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?

Single sentence that efficiently conveys purpose and output. No wasted words. Appropriate length for the tool's simplicity.

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

Completeness3/5

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

Given 5 optional parameters and no output schema, the description lacks details on parameter interaction (e.g., date vs. startDate/endDate exclusivity), pagination, or default sorting. Does not fully equip an agent to use the tool correctly.

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?

Parameter descriptions in schema are already detailed (100% coverage). The tool description adds no extra meaning beyond summarizing the output. Baseline 3 is appropriate since schema does the heavy lifting.

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?

Description clearly states verb 'Get', resource 'MLB game schedule', and specifies scope 'for a date or date range'. It also lists output contents (scores, status, teams). This distinguishes it from sibling tools like mlb_get_game which returns a single game detail.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like mlb_get_game or other schedule tools. No mention of prerequisites or exclusions (e.g., date parameters are mutually exclusive?). Agents are left to infer usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lacausecrypto/mcp-sports-hub'

If you have feedback or need assistance with the MCP directory API, please join our Discord server