Skip to main content
Glama
DanielTomaro13

sportsdata-mcp

pandascore_players

Read-onlyIdempotent

Retrieve esports player profiles with role, nationality, and current team. Filter by video game or search by name for targeted results.

Instructions

Esports players with role, nationality and current team.

Returns: [{id, name, first_name, last_name, role, nationality, image_url, current_team:{id, name, acronym}, current_videogame}] — SHAPE FROM VENDOR DOCS.

NOTE: this shape is from the vendor's documentation and has NOT been verified against a live response (we hold no key for this provider). Treat it as approximate — inspect the actual payload before relying on a field name.

Example: Dota 2 players {"filter_videogame": "dota2"}

Auth: needs your own key in PANDASCORE_TOKEN.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number.
per_pageNoPage size (max 100).
search_nameNoPartial name match.
filter_videogameNoTitle slug.
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds valuable context beyond that: the exact return shape (fields and nesting), a prominent caveat that the shape is unverified from vendor docs, and the authentication requirement via PANDASCORE_TOKEN.

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 compact and well-structured: a one-line summary, return shape, verification note, example, and auth requirement. Every sentence carries necessary information with no fluff, making it easy to scan.

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 four documented parameters, read-only hints, and no output schema, the description provides a full picture: return shape, example, and auth. It does not explain pagination behavior in detail or how to discover videogame slugs, but given the moderate complexity and existing annotations, it is sufficiently complete.

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 covers all four parameters with descriptions (100% coverage), so the baseline is 3. The description adds an example for filter_videogame and implies pagination through page/per_page, but it does not enrich parameter understanding significantly beyond 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 opens with 'Esports players with role, nationality and current team,' which clearly identifies the resource (esports players) and the fields returned. It differentiates from sibling tools like pandascore_teams and pandascore_matches by focusing on players, though it lacks an explicit verb like 'list' or 'retrieve'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The example 'Dota 2 players {"filter_videogame": "dota2"}' provides concrete context for when to use the tool and how to filter by videogame. However, it does not mention alternatives or when not to use this tool, stopping short of the explicit guidance that earns a 5.

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