Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_profile

Fetch a Sportskeeda player or team profile by slug to get names, facts, descriptions, and news cards in JSON.

Instructions

Get a Sportskeeda player or team profile. Returns a Sportskeeda player or team profile by host-free slug, such as player/jannik-sinner or nfl/green-bay-packers. The response has its name, kind, a description, fact rows as name and value pairs (names vary by sport), and any news cards. A page without fact rows returns an upstream error.

Input Schema

NameRequiredDescriptionDefault
slugYesSportskeeda player or team profile path without host

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the response shape (name, kind, description, fact rows as name/value pairs, news cards) and an important edge case, that a page without fact rows returns an upstream error. It omits auth or rate-limit context, so it stops short of a 5.

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 front-loaded sentences with no waste: purpose first, then slug format examples, then response/error behavior. Every sentence earns its place.

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 no output schema and no annotations, the description compensates by describing the return fields and an error condition. It is largely complete for a single-parameter lookup tool, though it could say more about what 'kind' values or fact rows look like per sport.

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%, so baseline is 3, but the description goes beyond the schema by giving two concrete slug formats ('player/...' and 'nfl/...') and clarifying the value is host-free. That extra format guidance genuinely reduces invocation error.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Get') and resource ('Sportskeeda player or team profile'), and gives concrete slug examples ('player/jannik-sinner', 'nfl/green-bay-packers') that pin down exactly what entity is retrieved. An agent can distinguish this from sibling tools like sportskeeda_player_stats or sportskeeda_wiki_article without opening a schema.

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?

Usage is implied by the slug examples, which show the expected input shape, but the description never says when to choose this over alternatives (e.g. sportskeeda_player_stats for stats) or what prerequisites exist. Adequate but with a clear gap in routing guidance.

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