Fetch a Sportskeeda player or team profile from a public path slug, returning facts and available news cards for sport-specific research and updates.
Get a Sportskeeda player or team profile. Returns facts and available news cards from a public player or team profile path, including sport-specific slugs.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Sportskeeda player or team profile path without host |
Changes observed during successful MCP inspections.
v1.17.7Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, so the description carries the full burden. It hints at return content ('facts and available news cards') but says nothing about auth requirements, rate limits, or what a missing/invalid slug yields. 'available' implies variable content but is not explained.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two efficient sentences with the core action front-loaded. No filler, though the second sentence slightly overlaps the first.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With a single required param, no annotations, and no output schema, the description is adequate but thin: it names the return categories yet gives no slug syntax. It is enough to call the tool, but an agent gets no help constructing a valid slug.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the schema already documents the slug. The description adds light color ('public player or team profile path', 'sport-specific slugs') but no format example or distinction between player vs team slug shapes. Baseline 3 fits.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource ('Get a Sportskeeda player or team profile') and clarifies the return content. It distinguishes player/team profiles from sibling content tools like sportskeeda_article, though it does not explicitly name any sibling.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance and no alternatives named despite many sportskeeda_profile-adjacent siblings (sportskeeda_player_stats, sportskeeda_taxonomy_search, sportskeeda_author). The agent must infer when this profile lookup is preferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.