Crawlora MCP

sofascore_referee_statistics

Read-only

Returns a SofaScore referee's record per competition: matches officiated, yellow cards, red cards, yellow-red cards and penalties awarded. Use it for discipline tendencies by referee id; an empty list is valid for a referee with no recorded competitions.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	Required. Numeric SofaScore referee id, e.g. 74264. Take it from the referee.id of the event endpoint or from a search result of type referee.

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 a genuinely useful behavioral note that an empty list is a valid response for referees with no recorded competitions, which prevents the agent from treating an empty result as an error. It does not discuss freshness or coverage limits of the aggregate record.

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 with zero filler: the first defines the payload fields, the second gives usage and the empty-result caveat. Content is front-loaded on what the tool returns.

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 needn't describe the response shape, and it correctly covers the input source, the metrics, and the empty-list case. A minor gap is the absence of any pointer to the sibling referee tools for the cases this one does not cover.

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% and the single id parameter is already documented in the schema with format, an example (74264) and sourcing instructions. The description adds nothing about the id beyond what structured data 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.

Purpose4/5

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

States a specific verb (Returns) plus the exact resource (a referee's record per competition) and enumerates the metrics returned: matches officiated, yellow/red/yellow-red cards, penalties awarded. It distinguishes itself from sofascore_referee and sofascore_referee_events by scope (per-competition aggregate record), though it never names those siblings explicitly.

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 discipline tendencies by referee id" gives clear when-to-use context tied to the required id parameter. It stops short of naming alternatives such as sofascore_referee (profile) or sofascore_referee_events (match list), so the routing decision is left partly to inference.

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.