Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_referee

SofaScore referee profile. Returns a referee's profile: name, country, sport, career matches officiated and career yellow, red and yellow-red card totals, plus date of birth and first league debut when SofaScore records them.

Instructions

SofaScore referee profile. Returns a referee's profile: name, country, sport, career matches officiated and career yellow, red and yellow-red card totals, plus date of birth and first league debut when SofaScore records them. Get the referee id from the referee.id of the sofascore-event endpoint or from a sofascore-search result of type referee. Returns 404 for an unknown id.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric SofaScore referee id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the 404 behavior for unknown ids and flags that DOB and first-league-debut are only present "when SofaScore records them" (nullable fields). It does not describe response shape or any rate-limit/caching behavior, but for a safe read-only lookup the coverage is solid.

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 the return payload, then id provenance, then error behavior. No filler and no redundancy with the schema.

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?

There is no output schema, so the description correctly enumerates the returned fields and their conditional nature, plus the error case and id sourcing. An agent has everything needed to call it and interpret the result.

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 types the id as a numeric string, so baseline is 3. The description adds real value beyond the schema by explaining where the id originates (event endpoint or search), which the field description alone does not convey.

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+resource ("Returns a referee's profile") and enumerates exactly which fields come back (name, country, sport, career matches, card totals, DOB, debut). It is trivially distinguishable from the sibling lookup tools like sofascore_referee_events and sofascore_referee_statistics, which cover history and stats rather than identity.

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 actionable context on how to source the required id (from sofascore-event's `referee.id` or a sofascore-search result of type referee), which is the main practical hurdle. It does not explicitly state when to prefer this tool over sofascore_referee_events/sofascore_referee_statistics, 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.

Deploy Server

Other Tools