Crawlora MCP

sofascore_referee

Read-only

Returns a SofaScore referee's profile: name, country, career matches and career yellow, red and yellow-red card totals, plus date of birth and first league debut when known. Requires a referee id, taken from the referee of sofascore_event or a sofascore_search result of type referee; an unknown id 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"
  }
}

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

A3.9/5.0

Behavior4/5

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

Annotations already cover read-only/open-world, but the description adds genuine behavioral detail beyond them: fields are returned conditionally ('first league debut when known') and an unknown id yields 'not found'. This is useful failure-mode disclosure for an otherwise thin read tool.

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?

Roughly two sentences, field list front-loaded, then the id requirement and error behavior. No filler, nothing redundant.

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 explain return values, and it covers the input source and failure case adequately. It is essentially complete for a single-parameter read tool, with only the sibling differentiation left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already documents the id. The description nonetheless reinforces and slightly extends the parameter meaning by spelling out the two acceptable sources for the id, which helps an agent avoid guessing.

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 and resource ('Returns a SofaScore referee's profile') and enumerates the returned fields (name, country, career matches, card totals, DOB, debut), which clearly separates it from siblings like sofascore_referee_events and sofascore_referee_statistics. It does not explicitly name those siblings, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the id provenance (from a sofascore_event referee or a search result of type referee) and the failure behavior for an unknown id, which is useful context. However, it never says when to choose this profile tool over the referee_events or referee_statistics siblings, so the routing guidance is only implied.

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.