Skip to main content
Glama
Sign In
MLB Stats MCP

MLB Stats MCP

by prnv-13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_team_roster

Read-onlyIdempotent

Retrieve a team's active, 40-man, or full-season roster by name, abbreviation, or ID for any season. Use it to discover players and build rosters for analysis.

Instructions

Get a team's roster.

Args:
    team: Team name, abbreviation or id, e.g. "Dodgers", "LAD" or "119".
    roster_type: "active" (26-man), "40Man", or "fullSeason" (everyone who played that season).
    season: Season year; defaults to the current one.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "team": "<team>"
    },
    "name": "get_team_roster"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamYes
seasonNo
roster_typeNoactive

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds useful context that season defaults to the current year and clarifies roster_type semantics, but says nothing about response size, pagination, or failure behavior for unknown teams.

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?

Front-loaded with the one-line purpose, then a compact Args list in parameter order. Minor waste in restating the season default already present in the schema, but nothing bloated.

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?

With an output schema present, return values need not be described; the remaining burden is parameter semantics and selection context, which are largely covered. Only explicit usage boundaries and error behavior are absent.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry all parameter meaning—and it does: team accepts name, abbreviation or numeric id with concrete examples, roster_type enumerates all three values with definitions, and season's default is restated. An agent can populate every parameter correctly from the description alone.

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 a team's roster'), which is clearly distinct from siblings like get_standings, get_schedule, or get_player_stats. It stops short of naming a sibling or boundary condition, so differentiation is implied rather than explicit.

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?

The roster_type explanations imply when each variant applies (26-man active vs 40-man vs everyone who played that season), but there is no explicit when-to-use guidance and no mention of alternatives or edge cases such as invalid team names or seasons before a franchise existed.

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