Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sofascore_team_transfers

Fetch a team's recent incoming and outgoing transfers with player, clubs, date, fee, and transfer type codes for transfer-window tracking.

Instructions

SofaScore team transfers. Returns a team's recent incoming (transfers_in) and outgoing (transfers_out) transfers with player, clubs, date, fee, and SofaScore's numeric transfer type code. Empty lists are valid for a quiet transfer window. Returns 404 when SofaScore has no transfer record for the team (seen for ice hockey and baseball teams). The type_code values are SofaScore's own opaque codes and are not translated.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric SofaScore team id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A3.8/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 meaningfully: it discloses that empty lists are legitimate (a quiet transfer window), that a 404 signals no record (seen for ice hockey and baseball teams), and that type_code values are opaque and untranslated. It does not mention auth or rate limits, but the failure-mode and data-shape disclosures are genuinely valuable.

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?

Four tight sentences: identity, return shape, empty-list semantics, then failure and caveat notes. The essential scoping information is front-loaded and no sentence is filler.

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, the description correctly compensates by enumerating the returned fields and the two top-level lists, and it covers the main error case. It stops short of saying how far back 'recent' transfers go or whether results are paginated, which is a minor gap for a one-parameter lookup tool.

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?

There is a single parameter with 100% schema description coverage ('Numeric SofaScore team id'), so the schema already documents it fully. The description adds no extra meaning about the id (e.g., how to obtain it or whether other sports use different id spaces), leaving this at the baseline for high schema coverage.

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?

The description names a specific resource and scope: a team's recent incoming and outgoing transfers, with the exact fields returned (player, clubs, date, fee, type code). An agent can tell this is team-level transfer history rather than match, roster, or statistics data. It does not, however, explicitly contrast itself with a sibling such as sofascore_player_transfers.

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?

Usage is implied by the resource ('team transfers' keyed by team id) but the description never states when to choose this over related SofaScore tools, nor any prerequisite for obtaining the team id. The 404 note gives a useful pre-condition for what kind of teams are supported, but there is no explicit when/when-not routing 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