Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

sportskeeda_salary_cap

Read-only

Read an NFL team's published salary-cap season, team totals, player cap scenarios and expanded pay breakdown. Supply the host-free salary-cap page slug; optional player search and column sorting operate on all published rows. A page with blank amounts and no players returns status no_data; the source season can lag the current season.

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_salary_cap"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoCase-insensitive player-name substring, at most 100 characters
slugYesNFL team salary-cap page path without host
orderNoSort direction; requires sort_by; default asc. Documented values: asc, desc.
sort_byNoSortable column; omit to preserve source order. Documented values: player, cap_number, cut_pre_june_1_dead_money, cut_pre_june_1_cap_saving, cut_post_june_1_dead_money, cut_post_june_1_cap_saving, trade_pre_june_1_dead_money, trade_pre_june_1_cap_saving, trade_post_june_1_dead_money, trade_post_june_1_cap_saving, restructure_cap_saving, extension_cap_saving.

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. Changed4 schema fields changed
    • addedInput schema / properties / order / description
      Added value: +"Sort direction; requires sort_by; default asc. Documented values: asc, desc."
    • addedInput schema / properties / q / description
      Added value: +"Case-insensitive player-name substring, at most 100 characters"
    • addedInput schema / properties / slug / description
      Added value: +"NFL team salary-cap page path without host"
    • addedInput schema / properties / sort_by / description
      Added value: +"Sortable column; omit to preserve source order. Documented values: player, cap_number, cut_pre_june_1_dead_money, cut_pre_june_1_cap_saving, cut_post_june_1_dead_money, cut_post_june_1_cap_saving, trade_pre_june_1_dead_money, trade_pre_june_1_cap_saving, trade_post_june_1_dead_money, trade_post_june_1_cap_saving, restructure_cap_saving, extension_cap_saving."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover readOnly/openWorld, so the bar is lower, yet the description adds genuinely useful behavior: a blank page yields a no_data status, and the source season can lag the current season. These are non-obvious traits not derivable from the annotations or schema.

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?

Three tight sentences, front-loaded with the core resource and followed by the required input, optional-param scope, and two edge-case notes. Every sentence carries information; only slightly dense on caveats.

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?

Rich structured support (100% param coverage, an output schema, annotations) means the description only needs to add edge-case and scope context, which it does via the no_data status and season-lag warning. Minor gap: no explicit indication of pagination or how to discover the slug.

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 would be 3, but the description adds real meaning by clarifying that search and sorting operate across all published rows rather than a visible subset, which the schema does not say.

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 (Read) and resource (an NFL team's published salary-cap season) plus the granular content it returns (team totals, player cap scenarios, expanded pay breakdown). An agent can distinguish this from siblings like sportskeeda_trade_values or sportskeeda_depth_chart, though it does not name a sibling directly.

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?

It says what to supply (the host-free salary-cap page slug) and what the optional params do, which implies the usage context. However it never states when to prefer this over adjacent sportskeeda tools or what prerequisites (e.g. how to obtain the slug) are needed.

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