Crawlora MCP

sofascore_tournament_cuptree

Read-only

Returns the knockout tree(s) of a SofaScore cup or playoff competition season: every round with its ties, the participants, winner, result and score strings (shoot-outs included), match ids and start times, plus the final and third-place tie; tennis returns a main and a qualifying tree. League seasons have no tree and return not found. Use sofascore_tournaments_with_feature to find competitions with a tree.

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": {
      "id": "<id>",
      "season": "<season>"
    },
    "name": "sofascore_tournament_cuptree"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Required. Numeric SofaScore unique-tournament (competition) id of a cup or knockout competition, e.g. 19 for the FA Cup, 7 for the UEFA Champions League, 132 for the NBA.
`season`	Yes	Required. Numeric SofaScore season id (from tournament-seasons), e.g. 82557 for the 2025/26 FA Cup.

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.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds real behavioral context: the coverage of the return (rounds, ties, winners, shoot-outs, match ids, start times, final/third-place tie) and the not-found behavior for league seasons. Listing return fields overlaps the output schema, keeping it just below 5.

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 the core purpose and edge cases packed into one dense block with little padding. Slightly long because it re-enumerates return fields that the output schema already carries, but nothing is truly wasted.

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?

For a two-param read tool with full schema coverage and an output schema, the description supplies what structured fields can't: the semantic scope of the tree, sport-specific variation (tennis main/qualifying), and the league not-found case. An agent has everything needed to call it correctly.

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 both parameters (id, season) are fully documented with examples in the schema. The description adds no syntax or format meaning beyond what the schema already provides, so the baseline of 3 applies.

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 ("knockout tree(s) of a SofaScore cup or playoff competition season") with precise scope, and names the sibling sofascore_tournaments_with_feature. An agent can distinguish this from standings/rounds/events tools 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly bounds applicability (cups/playoffs, tennis main+qualifying), states an exclusion (league seasons have no tree and return not found), and routes to the alternative sofascore_tournaments_with_feature to discover competitions with a tree. When-to-use and when-not are both covered.

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?