Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_draft_picks_options

Retrieve all available NFL draft filters for a Sportskeeda team page, returning years, rounds, positions, and historical special rounds from its public JSON asset.

Instructions

Discover an NFL team's complete Sportskeeda draft filters. Reads the public draft JSON asset named by the team page and returns every available year, round and position, including historical special rounds. Team page slugs are discoverable from page-options on an NFL team overview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesNFL team draft-picks page path without host

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries full behavioral burden. It discloses that the tool reads a public JSON asset and enumerates every available year/round/position including special historical rounds, implying a safe read. It stops short of explicitly stating there are no side effects and says nothing about rate limits, caching, or payload size.

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?

Three sentences, front-loaded with the core purpose followed by source and slug-provenance details. Minimal waste, though the middle sentence about 'historical special rounds' is a niche detail that could be trimmed.

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

Completeness3/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 must do more. It signals the returned categories (year, round, position) and how to obtain the slug, but does not describe the shape of the response or confirm it is purely enumerated filter values, leaving some gaps for an agent planning a follow-up call.

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% and the single slug parameter is fully documented ('NFL team draft-picks page path without host'), so the baseline is 3. The description adds where the slug originates (page-options on a team overview), but this slightly conflicts with the schema's 'draft-picks page path' wording, muddying rather than sharpening the parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Discover') and resource ('draft filters') and clarifies it returns enumerable filter values (year, round, position) rather than the picks themselves. This meaningfully distinguishes it from the sibling sportskeeda_draft_picks, though it never names that sibling explicitly.

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?

It supplies a prerequisite hint ('Team page slugs are discoverable from page-options on an NFL team overview'), which helps an agent obtain the required slug. However it never states when to prefer this over sportskeeda_draft_picks or that it is a precursor step for filtering picks, so the workflow relationship is only implied.

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