Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

sofascore_draft

Instructions

SofaScore league draft. Returns the draft attached to a league season: the upcoming or just-held draft and the previous_draft, each with its year, start and end time, status, the draft rounds (the valid round values for draft-picks) and whether the lottery is complete. The league enum accepts nba and nfl. Get season from tournament-seasons (NBA competition id 132, NFL 9464). A season without a draft, or a season id that does not belong to the league, returns 404. A season whose draft is not scheduled yet returns only previous_draft.

Input Schema

Name	Required	Description	Default
`league`	Yes	League whose draft to return
`season`	Yes	Numeric SofaScore season id of the league

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.12Oct 13, 2026

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 behavioral burden and does so well: it discloses the 404 conditions (season without a draft, or season id not belonging to the league) and the partial-return case (unscheduled draft returns only `previous_draft`). It does not explicitly confirm read-only status, but 'Returns' implies it.

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?

Front-loaded with purpose, then parameters, then error/edge behavior. It is dense but each sentence (return shape, enum, season source, 404 cases, partial return) earns its place; no filler.

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?

No output schema exists, so the description must (and does) explain return values: draft/previous_draft fields, rounds, and lottery status. Combined with the documented error conditions, an agent has enough to invoke and interpret results correctly.

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 already 100%, so the baseline is 3, but the description adds meaningful semantics beyond the schema: it tells the agent where to source `season` (tournament-seasons, competition ids 132/9464) rather than just restating that it is a numeric season id.

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 ('Returns the draft attached to a league season') and enumerates the exact payload (upcoming/just-held `draft`, `previous_draft`, year, times, status, `rounds`, lottery completion). It reads as a distinct retrieve-draft tool, clearly separable from the sibling `sofascore_draft_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 concrete prerequisite context: the `league` enum values and where to obtain `season` via tournament-seasons with NBA competition id 132 and NFL 9464. It does not name an alternative tool or a when-not-to-use rule, so it is clear context rather than full routing guidance.

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

Deploy Server

sofascore_draft

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools