Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_trade_values

Fetch NFL redraft or dynasty trade values by chart, scoring, position, and superflex, returning ranks, values, update time, and player slugs.

Instructions

Get NFL redraft or dynasty trade values. Reads the same anonymous JSON asset as the public chart. Returns source update time, ranks, values, and linked player slugs. The All position includes all source rows, including positions not displayed as chart sections. Discover current chart and filter choices with page-options.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesChart path without host
limitNoPage size from 1 to 500
offsetNoZero-based player offset
scoringNoScoring system; defaults to ppr
positionNoDisplayed position section; defaults to All
superflexNoUse superflex chart; defaults to false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does reasonably well: it discloses that the tool reads the same anonymous JSON asset as the public chart (implying no auth), what fields are returned (source update time, ranks, values, linked player slugs), and the 'All' position row-expansion quirk. It lacks detail on rate limits or pagination behavior.

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 front-loaded sentences with no filler; purpose, data source, return shape, and the option-discovery pointer come in a logical order. Slightly longer than strictly needed but each sentence adds information.

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 or annotations, the description compensates by naming the returned fields and the data source. Combined with a fully documented input schema, an agent has enough to invoke correctly, though return-format detail (pagination, ordering) is thin.

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 the baseline would be 3, but the description adds meaning beyond the schema by explaining that the All position returns all source rows, including positions not shown as chart sections – a behavioral nuance the enum value alone does not convey.

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 leads with a specific verb and resource: 'Get NFL redraft or dynasty trade values.' It also names the sibling to use for discovery ('page-options'), so an agent can distinguish this 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 Guidelines4/5

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

It tells the agent to 'Discover current chart and filter choices with page-options,' which is a concrete pointer to a sibling for option enumeration. It does not state explicit when-not-to-use conditions or alternative value sources, so it falls short of a full 5.

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