Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_team

Fetch a sports team profile from SofaScore by numeric ID to get name, country, sport, manager, venue, colors, national-team flag, and primary tournament.

Instructions

SofaScore team detail. Returns one SofaScore team by numeric id: name, short name, country, sport, manager, venue with its city and capacity, primary colour, and national-team flag. tournament_id and tournament_name give the team's primary competition, such as its domestic league. An unknown id returns an upstream error.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric SofaScore team id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.5/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 the error behavior for an unknown id and enumerates the fields surfaced (name, short name, country, sport, manager, venue/city/capacity, colour, national-team flag). It omits any mention of auth, rate limits, or caching, which keeps it short of a 5.

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?

Three front-loaded sentences: the purpose leads, the field enumeration follows, and an edge case closes. Every sentence earns its place, though the field list is slightly long given the tool's simplicity.

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 output schema and no annotations, the return-field enumeration and the unknown-id error note are exactly the missing context an agent needs. Coverage is good; only the absence of pagination/permission notes keeps it from the top.

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% for the single `id` parameter, so baseline is 3. The description restates 'numeric `id`' without adding syntax, range, or format guidance beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Returns one SofaScore team by numeric `id`') and enumerates the exact fields returned, so the agent knows it is a single-entity detail fetch rather than a list or search. It does not explicitly name or differentiate itself from sibling team-scoped tools (sofascore_team_events, sofascore_team_players, sofascore_team_transfers), which prevents a full 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no sibling alternative is named. The only actionable context is the derived note about tournament_id/tournament_name and the error-on-unknown-id note, which is input handling rather than usage guidance.

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