Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

sportskeeda_trade_values

Read-only

Get paginated NFL redraft or dynasty ranking rows from the public trade chart JSON, with scoring, position, and superflex filters. Discover accepted 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_trade_values"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesChart path without host. Documented values: nfl/fantasy-football-trade-value-charts, nfl/dynasty-trade-value-charts.
limitNoPage size from 1 to 500
offsetNoZero-based player offset
scoringNoScoring system; defaults to ppr. Documented values: ppr, non_ppr, 0.5_ppr.
positionNoDisplayed position section; defaults to All. Documented values: All, QB, RB, WR, TE.
superflexNoUse superflex chart; defaults to false

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. Changed6 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Page size from 1 to 500"
    • addedInput schema / properties / offset / description
      Added value: +"Zero-based player offset"
    • addedInput schema / properties / position / description
      Added value: +"Displayed position section; defaults to All. Documented values: All, QB, RB, WR, TE."
    • addedInput schema / properties / scoring / description
      Added value: +"Scoring system; defaults to ppr. Documented values: ppr, non_ppr, 0.5_ppr."
    • addedInput schema / properties / slug / description
      Added value: +"Chart path without host. Documented values: nfl/fantasy-football-trade-value-charts, nfl/dynasty-trade-value-charts."
    • addedInput schema / properties / superflex / description
      Added value: +"Use superflex chart; defaults to false"
  2. First observed

TDQS

A4/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 safe-read profile is covered. The description adds that data comes from a 'public trade chart JSON' and is paginated, but does not disclose page-size limits, offset behavior, or ordering of results beyond what the schema says.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core verb and resource, then the discovery hint. Nothing is redundant or padded.

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?

An output schema exists, so return values need not be described, and the schema covers all six parameters; the only residual gap is the absence of any statement about ordering or how pagination interacts with result counts.

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%, including enumerated slug, scoring, and position values, so the schema already carries the parameter meaning. The description restates the filter axes (scoring, position, superflex) but adds no syntax or default details beyond the schema, matching the baseline of 3.

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 paginated ... ranking rows') plus the resource (NFL redraft/dynasty trade chart) and names the filter dimensions, so an agent can distinguish it from sibling sportskeeda data 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 Guidelines4/5

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

It routes the agent to sportskeeda_page_options to discover accepted slug values, which is genuinely useful navigation guidance, but it never states when this tool should be chosen over, or instead of, other sportskeeda ranking/depth-chart tools.

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