Skip to main content
Glama
DanielTomaro13

sportsdata-mcp

mlb_transactions

Retrieve MLB roster transactions including signings, trades, call-ups, and IL moves. Filter by team, player, or date range.

Instructions

Roster transactions — signings, trades, call-ups, IL moves, DFA, etc. Filter by team, player, single date or date range.

Returns: {transactions:[{id, person, fromTeam, toTeam, date, typeCode, typeDesc, description]}]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNo
teamIdNo
endDateNo
sportIdNo
playerIdNo
startDateNo
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 discloses the return structure inline, which is good, but lacks details on pagination, rate limits, authentication, or whether the data is historical only. The return type is partially documented.

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?

The description is very concise (3 lines), front-loaded with the main purpose, and includes a useful return structure. Every sentence adds value with no redundancy.

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?

No output schema is provided, but the inline return structure helps. However, the description lacks details about pagination, error behavior, and the full scope of transactions (e.g., historical range). Given the 6 optional parameters, more completeness would improve usability.

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?

The description explains several parameters (team, player, date/date range) corresponding to teamId, playerId, date/startDate/endDate, but misses the sportId parameter entirely. With 0% schema coverage, more complete coverage would be expected. The description adds meaning but is incomplete.

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 clearly states the tool returns roster transactions (signings, trades, etc.) and lists filters. However, it does not differentiate from sibling tools like mlb_free_agents or mlb_people, so it's slightly less than a perfect 5.

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?

The description implies usage via filters but provides no explicit guidance on when to use this tool vs alternatives (e.g., mlb_free_agents for free agents only). No conditions or exclusions are mentioned.

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/DanielTomaro13/sportsdata-mcp'

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