Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

sportskeeda_player_stats

Read-only

Get NFL or NBA player season statistics from a player stats page, optionally filtered by a page-offered event phase. Discover phase values with sportskeeda_page_options.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "sportskeeda_player_stats"
  }
}

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. Documented values: 0, 1, 2, 3.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / event_type / description
      Added value: +"Event phase offered by this player's stats-event-type-dropdown; NFL offers 0,1,2,3 and NBA offers 0,1,2. Documented values: 0, 1, 2, 3."
    • addedInput schema / properties / slug / description
      Added value: +"NFL or NBA player stats path without host"
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the constraint that event phases are 'page-offered' (NFL 0,1,2,3 vs NBA 0,1,2), which is genuine context, though it says nothing about auth, rate limits, or the shape of the returned statistics.

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?

Two tight sentences with the core purpose front-loaded and the parameter guidance appended. Almost every clause earns its place, though the first sentence is slightly run-on.

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 an output schema present and annotations covering safety, the description needn't explain returns or permissions. It covers purpose, filtering, and value discovery, leaving only minor gaps such as what the slug format actually looks like or how phase affects output.

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 description coverage is 100%, so the baseline is 3. The description goes beyond the schema by explaining that valid event_type values are page-specific and pointing to sportskeeda_page_options for discovery, adding meaning the field's own description does not.

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 states a specific verb (Get) and resource (NFL or NBA player season statistics from a player stats page), which is far more informative than the tool name alone. It doesn't explicitly name the sibling it differs from (e.g., sportskeeda_page_data or sportskeeda_nba_queries), but the scope is clear enough to distinguish it.

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?

It gives concrete guidance for the optional parameter by routing the agent to sportskeeda_page_options to discover phase values. It stops short of stating when not to use this tool or naming a direct alternative for the core lookup.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources