Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_transactions

Retrieve MLB transactions for a required date range, covering signings, trades, options, assignments, injured-list moves, and releases; filter by team or player.

Instructions

List MLB transactions. Lists MLB transactions between start_date and end_date, both required in YYYY-MM-DD format. Covers signings, trades, options, assignments, injured-list moves and releases. Narrow with team_id or player_id. Each entry has the date, effective date, type, description, player, and from and to teams, with a total count.

Input Schema

NameRequiredDescriptionDefault
team_idNoNumeric MLB team id
end_dateYesRange end in YYYY-MM-DD format
player_idNoNumeric MLB player id
start_dateYesRange start in YYYY-MM-DD format

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the transactional categories covered (signings, trades, options, IL moves, releases) and enumerates the returned fields plus a total count, which is useful. It omits operational traits like pagination/result limits, ordering, and whether the range is inclusive, so it is adequate but incomplete.

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?

It is front-loaded with the primary action and sized appropriately for a four-parameter list tool. The opening two sentences are mildly redundant ("List MLB transactions. Lists MLB transactions between..."), a minor blemish rather than a real problem.

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 usefully compensates by describing the returned fields and total count. Together with a fully documented four-parameter schema and a clear scope, an agent has enough to call it correctly; only operational details like pagination are absent.

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 baseline is 3. The description restates the required date range and adds a modest filtering semantic for team_id/player_id beyond the schema's bare "Numeric MLB ... id", but does not clarify formatting or behavior beyond what the schema already provides.

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 opens with a specific verb+resource ("List MLB transactions") and immediately scopes it to a date range, making the operation unmistakable. It does not explicitly differentiate from nearby siblings such as sportskeeda_transactions or sofascore_player_transfers, so it falls short of a 5.

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 gives a concrete narrowing hint ("Narrow with `team_id` or `player_id`") and states both dates are required, which implies intended usage. However, it never names an alternative tool or says when to reach for this versus another transactions/filter source, so guidance is only implied.

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