Crawlora MCP

sofascore_referee_events

Read-only

Returns a page of 30 matches a SofaScore referee officiated, most recent first, across every competition. Requires a referee id; page is zero-based, so follow has_next_page for older pages. Only past matches exist, and a page past the end returns not found.

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_referee_events"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Required. Numeric SofaScore referee id, e.g. 74264.
`page`	No	Optional. Zero-based page number of officiated matches, 30 per page, most recent first. Defaults to 0. Follow has_next_page.

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

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real behavior beyond that: fixed page size of 30, reverse-chronological ordering, that only past matches exist, that an out-of-range page returns not found, and the has_next_page pagination contract.

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?

Three tight sentences, front-loaded with what is returned, then the required input, then the pagination and edge-case behavior. No wasted wording.

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?

With an output schema present the description needn't explain return fields, and it still covers ordering, page size, the has_next_page contract, and the not-found edge case. Nothing needed to call this tool correctly is missing.

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 already documented there, including the zero-based page and default of 0. The description only reiterates the zero-based page and the id requirement, adding no new syntax or format 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 (returns matches a referee officiated), pins down the scope (30 per page, most recent first, across every competition), which cleanly separates it from siblings like sofascore_referee and sofascore_referee_statistics.

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 clear operational context: a referee id is required, page is zero-based, and older pages are reached via has_next_page. It does not explicitly name the alternative tools (e.g. sofascore_referee_statistics) or say when this is preferred over them, so it stops short of full routing guidance.

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?