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.

Instructions

Get NFL or NBA player season stats across event phases. Reads the anonymous season-stats JSON embedded in an NFL or NBA player stats page. Without event_type, returns all event phases offered by that page's selector. NBA source data may contain extra internal 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

TableJSON 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

A4.5/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 that the read is of anonymous JSON (no auth needed), the default behavior when event_type is omitted, and the NBA-specific quirk where extra internal phases are silently excluded. It does not mention rate limits or output shape, but the behavioral disclosure is strong.

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 sentences, front-loaded with the core purpose and receiver, then the default behavior, then the NBA caveat, then the discovery pointer. Each sentence earns its place, though the NBA edge case adds some length for a niche scenario.

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, annotation-free tool with no output schema, the definition covers purpose, default behavior, source data characteristics, and how to discover valid event_type values. It stops short of hinting at the returned stat structure, which would round it out, but it is otherwise complete.

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 adds real meaning beyond the schema: it explains the omitted-event_type default ('returns all event phases') and reinforces the per-league phase availability. That is genuine semantic value over the enum's own description.

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 (NFL or NBA player season stats across event phases), and distinguishes itself from the sibling sportskeeda_page_options by naming it for event_type discovery. An agent can tell it apart from other sportskeeda_* tools without opening the schema.

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

Usage Guidelines5/5

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

Explicitly describes the no-event_type case (returns all event phases) versus the filtered case, and routes the agent to sportskeeda-page-options for discovering current event_type values. Nothing is left to inference about when to reach for this tool versus its sibling.

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