Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

sportskeeda_draft_picks

Read-only

List complete historical NFL team draft picks from the page's public JSON asset. Supply a host-free team draft-picks slug, use sportskeeda_draft_picks_options for exact filters, and page through the full result instead of relying on visible page rows.

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

Input Schema

NameRequiredDescriptionDefault
qNoCase-insensitive player-name substring, at most 100 characters
pageNoPage number, 1-1000; default 1
slugYesNFL team draft-picks page path without host
yearNoYear from draft-picks-options; omit for all years
roundNoExact round from draft-picks-options; historical special labels are accepted
per_pageNoRecords per page, 1-500; default 100
positionNoExact position from draft-picks-options

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. Changed7 schema fields changed
    • addedInput schema / properties / page / description
      Added value: +"Page number, 1-1000; default 1"
    • addedInput schema / properties / per_page / description
      Added value: +"Records per page, 1-500; default 100"
    • addedInput schema / properties / position / description
      Added value: +"Exact position from draft-picks-options"
    • addedInput schema / properties / q / description
      Added value: +"Case-insensitive player-name substring, at most 100 characters"
    • addedInput schema / properties / round / description
      Added value: +"Exact round from draft-picks-options; historical special labels are accepted"
    • addedInput schema / properties / slug / description
      Added value: +"NFL team draft-picks page path without host"
    • addedInput schema / properties / year / description
      Added value: +"Year from draft-picks-options; omit for all years"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds real behavioral context beyond them: the data comes from the page's public JSON asset and results should be paged rather than inferred from visible rows. It doesn't cover rate limits or response shape, but with annotations carrying the safety profile this is solid.

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 tightly packed sentences with zero waste; the core purpose is front-loaded and the routing/paging guidance follows immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 needn't be explained, and annotations cover safety. The description supplies the remaining operational essentials: slug format, filter-value source, and pagination behavior.

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 coverage is 100%, so the schema already documents all 7 parameters. The description restates the slug format ('host-free team draft-picks slug') and points filters at the options tool, adding only marginal meaning over 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?

States a specific verb and resource: 'List complete historical NFL team draft picks from the page's public JSON asset.' It also names the sibling it complements (sportskeeda_draft_picks_options), so an agent can distinguish it without opening a 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?

Explicitly routes filter-value lookups to sportskeeda_draft_picks_options and instructs paging 'through the full result instead of relying on visible page rows.' Clear context, though it does not state when this tool should be avoided entirely.

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