Crawlora MCP

sofascore_scheduled_events

Read-only

Returns the matches in one SofaScore category that start on a UTC date, ordered by start time with teams, status, and score. Use it for a country's fixtures on a day; requires a category id from sofascore_categories and a YYYY-MM-DD date.

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": {
      "category_id": "<category_id>",
      "date": "<date>"
    },
    "name": "sofascore_scheduled_events"
  }
}

Input Schema

Name	Required	Description	Default
`date`	Yes	Required. UTC calendar date as YYYY-MM-DD, e.g. 2026-10-08.
`category_id`	Yes	Required. Numeric SofaScore category id from sofascore_categories, e.g. 13 for Brazil football.

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

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real behavioral context beyond that: results are ordered by start time and the date is interpreted strictly as a UTC calendar day, which is a non-obvious constraint.

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, front-loaded with the core action and followed by the usage and prerequisite. 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?

With an output schema present, the description does not need to enumerate return values, yet it still sketches them (teams, status, score). Adding explicit routing against sibling event-listing tools would make it fully complete.

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 description coverage is 100%, so the schema already documents both parameters including the YYYY-MM-DD format and the category-id provenance. The description largely restates this, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (returns), resource (matches in one SofaScore category), and scope (starting on a UTC date), plus ordering and returned fields. It distinguishes itself from match-level siblings like sofascore_event, but does not explicitly contrast with the close sibling sofascore_scheduled_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?

"Use it for a country's fixtures on a day" gives a clear use context, and it names sofascore_categories as the prerequisite source for the category id. It stops short of naming alternatives or stating when not to use this tool.

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?