Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_salary_cap

Fetch NFL team salary-cap figures from Sportskeeda, including season totals, player cap scenarios, and salary breakdowns with searchable, sortable rows.

Instructions

Get NFL team salary-cap figures from Sportskeeda. Returns the source's published season, team totals, every player cap scenario and expanded salary breakdown. The site's player search and sortable columns are applied to the complete server-rendered rows. The published season may lag the current season.

Input Schema

TableJSON 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
sort_byNoSortable column; omit to preserve source order

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.9/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 behavioral burden and does useful work: it discloses that search/sort are applied server-side across the complete row set, and it warns that the published season may lag the current season, a genuine freshness caveat. It still omits any auth, rate-limit, or pagination 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 short sentences, front-loaded with the core purpose and return contents before the caveats. Every sentence contributes, though the 'expanded salary breakdown' phrasing is slightly redundant with the preceding enumeration.

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 does explain the return payload and the staleness caveat, which is what an agent most needs here. It is slightly thin on how the required slug should be formed and on any pagination limits, but overall adequate for a 4-parameter scraper endpoint.

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 description coverage is 100%, so the schema already documents q, slug, order, and sort_by with enums, establishing a baseline of 3. The description adds only loosely that 'player search and sortable columns are applied to the complete server-rendered rows,' which clarifies scope but adds no syntax or format detail beyond the schema.

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?

The description opens with a specific verb and resource ('Get NFL team salary-cap figures from Sportskeeda') and enumerates the returned data (season, team totals, player cap scenarios, salary breakdown). An agent can distinguish this from the many other sportskeeda_* siblings immediately.

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 required slug parameter and the mention that player search and sortable columns apply, but the description never states when to choose this tool over sibling sportskeeda endpoints or what prerequisites the slug implies. No explicit when/when-not guidance or named alternatives.

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