Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

sofascore_event_managers

SofaScore event managers. Returns the two managers (coaches) of a match with their SofaScore ids, names and slugs. The manager id works with the manager and manager-events endpoints.

Instructions

SofaScore event managers. Returns the two managers (coaches) of a match with their SofaScore ids, names and slugs. The manager id works with the manager and manager-events endpoints. Returns 404 when SofaScore lists no managers for the match, which includes tennis matches.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric SofaScore event (match) id

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?

No annotations are provided, so the description carries the full burden and does a good job: it discloses the return shape (two managers with ids, names, slugs), the cross-endpoint id contract, and the 404 condition including the tennis-match edge case. It omits any auth or rate-limit context, but for a read-only lookup this is solid disclosure.

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 resource and return shape, followed by the id contract and the error case. No filler and nothing that fails to earn its place.

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 no annotations and no output schema, the description must explain what comes back, and it does (two managers with ids, names, slugs) plus the 404 behavior. It is nearly complete for a simple one-param read tool; only richer behavioral detail (e.g., typical data availability) is absent.

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 coverage is 100% and the single `id` parameter is already documented as 'Numeric SofaScore event (match) id'. The description restates the event/match linkage and helpfully distinguishes the output manager id from the input, but adds little syntax-level meaning to the parameter itself. 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 the two managers (coaches) of a match with their SofaScore ids, names and slugs.' It is distinguishable from siblings like sofascore_manager (a single manager) and sofascore_manager_events, and it even clarifies the downstream id relationship.

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?

The description implies usage (call with a match id to get that match's coaches) and notes the manager id feeds manager/manager-events endpoints, but it never explicitly says when to pick this over sibling endpoints such as lineups or statistics. Guidance is present but inferred rather than stated.

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