Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_manager_events

Retrieves a page of recent matches coached by a given SofaScore manager, newest first across all clubs. Use it to review a manager's past match history.

Instructions

SofaScore manager recent matches. Returns a page of the matches a manager (coach) has recently taken charge of, newest first, across all clubs they managed. Only past matches are available; SofaScore publishes no upcoming list for managers. Returns 404 for a page past the end of the manager's history.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric SofaScore manager id
pageNoZero-based page number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A4/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 well: it discloses ordering ('newest first'), scope ('across all clubs'), an availability constraint (past matches only), and an error behavior ('Returns 404 for a page past the end of the manager's history'). Missing only auth/rate-limit context, which is minor for a 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?

Three tight sentences, front-loaded with purpose followed by ordering/scope, availability, and the error case. No filler; each sentence adds usable information.

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?

For a 2-parameter paginated list tool with no annotations and no output schema, the description covers purpose, ordering, scope, availability, and the out-of-range error. It does not sketch the returned match fields, but that gap is small given the constrained surface.

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%, so both 'id' and 'page' are already documented in the schema. The description adds no parameter-level syntax or format beyond the schema (the 404 detail relates to paging but is behavioral, not semantic). Baseline 3 is appropriate.

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 a page of the matches a manager (coach) has recently taken charge of') and clarifies the scope ('across all clubs they managed'). This clearly distinguishes it from sibling event tools like sofascore_team_events or sofascore_player_events.

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?

Implies the use case (a manager's match history) and gives one negative constraint ('Only past matches are available; SofaScore publishes no upcoming list for managers'). However, it never names an alternative tool or states when to prefer this over sibling manager/event endpoints, leaving routing to inference.

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