Crawlora MCP

sofascore_scheduled_tournaments

Read-only

Returns a page of the tournaments that have fixtures on a UTC date for a sport, with the event count per tournament and a next-page flag. Use it to see which competitions play on a date; requires sport and a YYYY-MM-DD date, and sofascore_scheduled_events lists the matches.

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": {
      "sport": "<sport>",
      "date": "<date>"
    },
    "name": "sofascore_scheduled_tournaments"
  }
}

Input Schema

Name	Required	Description
`date`	Yes	Required. UTC calendar date as YYYY-MM-DD, e.g. 2026-10-08.
`page`	No	Optional. One-based page number. Defaults to 1; follow has_next_page for more.
`sport`	Yes	Required. Sport key. One of american-football, aussie-rules, badminton, bandy, baseball, basketball, beach-volley, cricket, darts, esports, floorball, football, futsal, handball, ice-hockey, mma, minifootball, padel, rugby, snooker, table-tennis, tennis, volleyball, waterpolo. Call sofascore_sports for the list.

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/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 adds that results include a per-tournament event count and a next-page flag, which is useful but overlaps with the output schema. No auth, rate-limit, or freshness caveats are added beyond the UTC-date scoping.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, and the return content and required-input constraint are front-loaded before the pointer to the sibling tool.

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?

For a read-only, 3-param, paginated list tool with a full output schema and full annotation coverage, the description supplies everything an agent needs to call it correctly. Minor gap: no hint about ordering or result size limits.

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%, so the schema already documents sport (with the enumerated keys), date format, and the one-based page/next-page behavior. The description only restates that sport and a YYYY-MM-DD date are required, adding no syntax or semantics beyond the structured fields. 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 ('Returns a page of the tournaments that have fixtures on a UTC date for a sport') and immediately distinguishes itself from the sibling sofascore_scheduled_events, which 'lists the matches'. An agent can tell the two apart without opening either schema.

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 a clear use case ('see which competitions play on a date') and routes to the alternative (sofascore_scheduled_events) for the match-level view. It does not state an explicit when-not condition, but the scoping is clear enough for correct selection.

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?