Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mlb_team_roster

Fetch an MLB team's roster with player names, jersey numbers, positions, and status by team ID; optionally set season and roster type.

Instructions

Get an MLB team roster. Returns a team's players, jersey numbers, positions, and roster status. The roster_type parameter accepts every value in the live MLB value set returned by mlb_discovery.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seasonNoFour-digit season; defaults to current year
team_idYesNumeric MLB team id
roster_typeNoRoster type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.7
    • changedInput schema / properties / roster_type / enum
      Previous value: -[
-  "active",
-  "40Man",
-  "fullSeason"
-]New value: +[
+  "40Man",
+  "fullSeason",
+  "fullRoster",
+  "nonRosterInvitees",
+  "active",
+  "allTime",
+  "depthChart",
+  "gameday",
+  "coach"
+]
  2. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / roster_type / enum
      Added value: +[
+  "active",
+  "40Man",
+  "fullSeason"
+]
  3. Added

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral load. It discloses returned data categories and flags that roster_type should be taken from a live MLB value set via mlb_discovery, but omits auth, rate-limit, pagination, and error behavior.

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?

Three short sentences, front-loaded with the action and return contents; no filler. Each sentence contributes directly to selecting or invoking the tool.

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 simple three-parameter read tool with no output schema and no annotations, the description covers purpose, returned fields, and the dynamic roster_type source. It is slightly incomplete on season defaulting (left to schema) and lacks operational details, but nothing critical for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, which sets a baseline of 3. The description adds non-schema meaning by stating that roster_type accepts every value in the live MLB value set returned by mlb_discovery, warning the agent that the schema enum may not be exhaustive.

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 'Get' and resource 'MLB team roster', and enumerates the returned fields: players, jersey numbers, positions, and roster status. It does not explicitly distinguish itself from sibling tools such as mlb_teams or mlb_team_stats, so it stops 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?

Provides an implied usage context (retrieve a team's roster) and a useful lookup hint: roster_type values come from mlb_discovery. It does not state when to choose this over mlb_teams, mlb_team_stats, or other roster-related siblings, nor any when-not conditions.

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