Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_player_stats

Retrieve NFL or NBA player season stats across event phases from a stats page; omit event_type to get all phases available for that player.

Instructions

Get NFL or NBA player season stats across event phases. Returns the season stats for an NFL or NBA player stats page. Without event_type, returns all event phases offered by that page's selector. NBA data may contain extra phases that the page does not offer; these are excluded. Discover the current event_type values with sportskeeda-page-options for the same slug.

Input Schema

NameRequiredDescriptionDefault
slugYesNFL or NBA player stats path without host
event_typeNoEvent phase offered by this player's stats-event-type-dropdown; NFL offers 0,1,2,3 and NBA offers 0,1,2

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior (default phase enumeration, NBA phases excluded from output). However, it omits pagination, error behavior, and return shape details, so it adds only partial behavioral context.

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?

Four front-loaded sentences, each contributing: purpose, return, default behavior, and value discovery. No filler, though the first two sentences overlap slightly on stating what is returned.

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 two-parameter tool with 100% schema coverage and no output schema, the description covers purpose, default behavior, and how to obtain valid enum values. Return-format detail is the only notable 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?

Schema coverage is 100%, so the schema already documents both parameters and their enum values, making the baseline 3. The description reinforces event_type's meaning and the no-event_type default, adding marginal value over 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?

States a specific verb ('Get') and resource ('NFL or NBA player season stats') and cross-references the sibling sportskeeda_page_options for discovery. It is clear what the tool returns, though the sibling differentiation is only implied via the discovery pointer rather than a direct contrast.

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?

Gives explicit conditional behavior: with event_type it returns that phase, without it returns all phases offered by the page selector. It also routes the agent to sportskeeda-page-options to discover valid event_type values, which is genuinely actionable guidance even if no explicit 'do not use' case is given.

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