Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_tournament_info

SofaScore competition info. Returns a competition's metadata (name, sport, category, tier, title holder, most titles, current season dates, divisions above and below, linked competitions).

Instructions

SofaScore competition info. Returns a competition's metadata (name, sport, category, tier, title holder, most titles, current season dates, divisions above and below, linked competitions). When season is given it also returns that season's aggregates: number of competitors and, for football competitions, goals, home wins, away wins, draws, yellow and red cards and the promoted teams. Get id from search and season from tournament-seasons.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric SofaScore unique-tournament (competition) id
seasonNoNumeric SofaScore season id. Omit for competition metadata only

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A4.4/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 so well: it discloses the full return payload, including that season aggregates are football-specific and that `season` changes what comes back. It never states safety profile, auth, or rate limits, but for a read-only info endpoint the substantive behavioral context (conditional response shape) is present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose, then the base payload, then the conditional season behavior. The long parenthetical field lists are verbose but earn their place because no output schema exists to document the response.

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?

The tool has no output schema, so the description must describe returns — and it does so thoroughly, covering both the base metadata and the optional season aggregates. Parameters are fully sourced and semantics are complete for a two-parameter info call.

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. The description goes beyond the schema by explaining that `season` is optional and materially changes the response (adding competitor counts and football aggregates), and it tells where `id` and `season` come from.

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 ('SofaScore competition info' / 'Returns a competition's metadata') and enumerates exactly what metadata is returned. This scope is clearly distinct from event, player, team, and standings tools, so an agent can identify it without opening the schema.

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?

Explicitly tells the agent how to obtain parameters ('Get `id` from search and `season` from tournament-seasons') and makes the conditional usage of `season` clear ('When `season` is given it also returns...'). It stops short of naming an alternative tool to use instead when only statistics are wanted, so no explicit exclusion.

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