Crawlora MCP

sportskeeda_draft_picks_options

Read-only

List every year, round and position in an NFL team's Sportskeeda draft history, including older special rounds. Supply a host-free team draft-picks page slug; use the returned values with sportskeeda_draft_picks.

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

Input Schema

Name	Required	Description	Default
`slug`	Yes	NFL team draft-picks page path without host

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026
- addedInput schema / properties / slug / description
```
Added value: +"NFL team draft-picks page path without host"
```
First observedOct 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld), and the description adds useful behavioral context beyond them: the tool enumerates available years/rounds/positions and notably includes older special rounds, which discloses coverage of the returned set. It does not cover pagination or response shape, but the output schema and annotations reduce that burden.

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 purpose and followed by the input/output contract. No filler; every clause carries information an agent needs.

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?

For a 1-parameter options tool with an output schema and safety annotations, the description is nearly complete: it says what is listed and how to chain it. The one gap is that it does not indicate where to obtain a valid team slug, which an agent would otherwise have to infer.

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?

Only one parameter with 100% schema coverage, so the baseline is 3. The description restates the slug requirement as 'host-free team draft-picks page slug', which mirrors the schema's 'NFL team draft-picks page path without host' with no added syntax, format example, or origin guidance.

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 (List) and resource (every year, round and position in an NFL team's Sportskeeda draft history) and explicitly distinguishes itself from the sibling sportskeeda_draft_picks by naming it as the consumer of the output. An agent can tell this is the enumeration/options tool 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?

Gives clear when-to-use context and a concrete next step: supply a host-free slug, then feed returned values into sportskeeda_draft_picks. The workflow relationship with the sibling is explicit, though no when-not-to-use or source-of-slug guidance is given.

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

All Crawlora MCP tools Inspect

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

Need Help?