Skip to main content
Glama
Sign In
sportsdata-mcp

sportsdata-mcp

by DanielTomaro13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

pl_player_season_stats

Read-onlyIdempotent

Retrieve a player's complete season statistics for a given competition and season, including Opta metrics, using player, competition, and season IDs.

Instructions

A player's stats for one season.

Returns: {player, stats:{…season Opta metrics}}

Auth: none needed.

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": {
      "cid": "<cid>",
      "sid": "<sid>",
      "pid": "<pid>"
    },
    "name": "pl_player_season_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
cidYesCompetition id (8). Required — part of the URL path.
pidYesPlayer id. Required — part of the URL path.
sidYesSeason id (2025 = 2025/26). Required — part of the URL path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.24.0
    • addedInput schema / properties / cid / description
      Added value: +"Competition id (8). Required — part of the URL path."
    • addedInput schema / properties / pid / description
      Added value: +"Player id. Required — part of the URL path."
    • addedInput schema / properties / sid / description
      Added value: +"Season id (2025 = 2025/26). Required — part of the URL path."
  2. Addedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, establishing the safety and openness of the operation. The description adds 'Auth: none needed' and a return shape, which are useful context, but it does not elaborate on what 'Opta metrics' includes or potential edge cases. This is modest additional value beyond annotations.

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 extremely concise: a one-line purpose, a return type summary, and an auth note. Every sentence serves a distinct purpose, and the most important information (what the tool returns) is front-loaded. No fluff or repetition.

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 read-only tool with all parameters documented in the schema and safety declared through annotations, the description is nearly complete: it states the purpose, the return shape, and auth requirements. It falls slightly short by not providing any usage guidance or caveats about data availability, but given the tool's simplicity, this is a minor gap.

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 input schema has 100% description coverage, with each parameter clearly explained (e.g., 'Competition id (8)', 'Player id', 'Season id'). The description adds no additional parameter-specific semantics, so it does not improve on the baseline established by the schema.

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 resource: 'A player's stats for one season.' This identifies the scope (single season) and the subject (player), which distinguishes it from broader player tools. However, it lacks an explicit verb like 'get' or 'retrieve', and does not reference sibling tools, so it is clear but not fully differentiated.

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 is provided about when to use this tool versus alternatives. The description does not mention any exclusions, prerequisites, or comparison to related tools like pl_player_comp_stats or pl_player_info. The agent is left to infer usefulness from the name and brief description.

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