Crawlora MCP

sofascore_draft_picks

Read-only

Returns one round of an NBA (rounds 1-2) or NFL (rounds 1-7) draft: each pick with overall and in-round number, drafting team and prospect (name, position, college, player id), plus teams without a pick. Requires league, a four-digit year from sofascore_draft and a round; older years that SofaScore no longer keeps return not found.

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": {
      "league": "<league>",
      "year": "<year>",
      "round": "<round>"
    },
    "name": "sofascore_draft_picks"
  }
}

Input Schema

Name	Required	Description
`year`	Yes	Required. Four-digit draft year from sofascore_draft (its draft.year or previous_draft.year), e.g. 2025.
`round`	Yes	Required. Draft round, 1 to 2 for nba and 1 to 7 for nfl. sofascore_draft lists the rounds.
`league`	Yes	Required. One of nba, nfl.

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.

AddedOct 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context beyond that: the per-league round ranges and the edge case that older years SofaScore no longer keeps return not found.

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?

A single dense sentence that front-loads the scope (one round of which drafts) before the required inputs and the not-found caveat. Every clause earns its place, though the run-on format and parenthetical field list are slightly heavy.

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 an output schema present, the description needn't detail return values, yet it summarizes the pick fields, plus covers required inputs, their source, and a failure mode. Complete enough for an agent to call correctly; only missing explicit sibling routing.

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 parameters are already documented, and the description largely repeats the round ranges. However it adds cross-tool meaning by stating the year must come from sofascore_draft (draft.year or previous_draft.year), which the schema also notes but the description reinforces as a workflow constraint.

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 (returns) and resource (one round of an NBA/NFL draft), and explicitly delineates scope with the round ranges per league. An agent can distinguish it from the sibling sofascore_draft, which lists the draft as a whole rather than one round of picks.

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 context: it depends on values sourced from sofascore_draft (the four-digit year and round), which implicitly routes the agent to that sibling first. It doesn't explicitly state when NOT to use it or name alternative tools, but the prerequisite chain is clear.

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?