Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_team_tournaments

SofaScore team competitions. Lists the competitions a team plays in, each with id, name, slug, category and sport. By default (all=false) it returns the competitions the team currently takes part in; with all=true it returns every…

Instructions

SofaScore team competitions. Lists the competitions a team plays in, each with id, name, slug, category and sport. By default (all=false) it returns the competitions the team currently takes part in; with all=true it returns every competition the team has been recorded in, including friendlies and older tournaments. Competition ids can be used as tournament_id elsewhere in the SofaScore endpoints; use team-player-statistics-seasons for the seasons that have statistics. Returns 404 when SofaScore has no competitions for the team.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric SofaScore team id
allNofalse returns current competitions, true returns every recorded competition

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 burden and does well: it discloses the default scope, the expanded scope including friendlies/older tournaments, and the 404 error condition. It omits auth/pagination traits, but the behavioral picture is solid for a read-only listing.

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?

Purpose is front-loaded and the sentences are tight, each covering a distinct facet (return shape, parameter branching, id reuse, error case). Slightly dense but no wasted sentences.

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?

With no output schema, the description compensates by describing the returned fields, the parameter branching, and the 404 failure mode. Nothing an agent needs in order to call this correctly is missing.

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 meaning beyond the schema: it expands `all=true` to include friendlies and older tournaments and explains that returned competition ids are reusable as `tournament_id` elsewhere. That cross-endpoint semantics is genuine added value.

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?

The description opens with a specific verb ("Lists") and resource ("the competitions a team plays in") and enumerates the returned fields (id, name, slug, category, sport). An agent can immediately tell this apart from the team_events or player_tournaments siblings.

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?

It clearly explains the current-vs-historical branching via `all`, and routes season-level needs to team-player-statistics-seasons. It stops short of naming competing siblings like sofascore_team_events for event listings, so it is clear context rather than full when/when-not coverage.

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