Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_referee_events

SofaScore referee officiated matches. Returns one page (30 matches) of the matches a referee officiated, most recent first, across every competition. Follow has_next_page for older pages; a page past the end returns 404.

Instructions

SofaScore referee officiated matches. Returns one page (30 matches) of the matches a referee officiated, most recent first, across every competition. Follow has_next_page for older pages; a page past the end returns 404. Only past matches exist (no upcoming list), and the list includes canceled and postponed fixtures (their status.type says so), which the career match total of sofascore-referee does not count.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric SofaScore referee id
pageNoZero-based page number. Defaults to 0

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and delivers: page size (30), sort order (most recent first), cross-competition scope, pagination via `has_next_page`, the 404 behavior past the end, that only past matches exist, and that canceled/postponed fixtures are included and indicated by `status.type`.

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?

Purpose is front-loaded in the first sentence, then pagination and edge cases follow. Four dense sentences with no filler, each contributing a distinct fact.

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?

No output schema exists, so the description must describe the return shape; it does so (30 matches per page, ordering, status.type for canceled/postponed, 404 boundary). Combined with 100% schema coverage of the two params, an agent has everything needed to call it correctly.

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%, so the baseline is 3, but the description adds real meaning about pagination — `page` advances via `has_next_page` and a page past the end returns 404 — which the schema's 'Zero-based page number' wording 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 and resource — matches a referee officiated — with the source named ('SofaScore referee officiated matches'). It also differentiates from the sibling sofascore_referee by noting its career total does not count these fixtures, so the two are distinguishable without opening schemas.

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?

Clearly implies when to use it (listing a referee's matches, most recent first, across competitions) and names the contrasting sibling behavior (career match total). It does not spell out explicit exclusions or alternatives like referee_statistics, so it stops short of a full 5.

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