Crawlora MCP

sofascore_team_tournaments

Read-only

Lists the competitions a SofaScore team plays in, each with id, name, slug, category and sport. By default it returns the current competitions; pass all=true for every competition the team has been recorded in, including friendlies and older tournaments. Use the ids as tournament_id in other SofaScore tools.

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>"
    },
    "name": "sofascore_team_tournaments"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Required. Numeric SofaScore team id, e.g. 17.
`all`	No	Optional. false (default) lists the competitions the team currently plays in; true lists every competition the team has been recorded in, including friendlies and older tournaments.

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

A3.9/5.0

Behavior3/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's scope statement about default vs all=true is genuinely useful but is verbatim identical to the schema description of the `all` parameter, so there is little behavioral information beyond structured fields.

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 short sentences, front-loaded with what is returned and the default scope. Slight redundancy with the schema's param description keeps it from a 5.

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?

An output schema exists, so return values need not be explained, and the description still names the returned fields. Combined with annotations covering the read-only profile and the explicit downstream-id guidance, the definition is essentially complete for a two-parameter list tool.

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 are documented there, including the exact default/true semantics. The description's parameter commentary duplicates the schema rather than adding format or constraint detail, so baseline 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 and resource (lists the competitions a SofaScore team plays in) and enumerates the returned fields. The scoping phrase 'a team plays in' also distinguishes it from sibling tools like sofascore_player_tournaments or sofascore_category_tournaments.

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?

Explains the two usage modes: default returns current competitions, all=true returns every recorded competition including friendlies and older tournaments. It also tells the agent what to do with the result ('Use the ids as tournament_id in other SofaScore tools'), but names no explicit alternative tool or exclusion rule.

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?