Skip to main content
Glama

SportStatsAPI

Get transfers

get_transfers
Read-only

Soccer transfers from player profiles: player, from and to team, date, season, window (summer, winter, other by the date), type (transfer, loan, loan_return, free, promoted, swap, unknown) and fee_eur where the feed gives an amount (often null: the fee is not known, not 0). Filter by league (moves in or out of its current teams), team (direction in or out), season and window; sort by fee for the biggest moves. Moves dated after today (mostly planned loan ends) are left out; planned true returns only those. Profiles are re-read every 30 days, so the latest moves can be missing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_transfers"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNodate (default, latest first) or fee (highest first)
limitNomaximum results (default 20, max 100)
seasonNo2026-27 (1 June to 31 May) or 2026 (calendar year)
windowNosummer (1 June-5 September), winter (1 January-3 February) or other
plannedNotrue: only agreed moves dated after today (mostly loan ends); default: moves up to today
team_idNomoves of this team
directionNowith team_id: in or out (default both)
league_idNomoves in or out of this league's current teams

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / league_id / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "string"
      +]
    • changedInput schema / properties / team_id / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "string"
      +]
  2. Added

TDQS

A3.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond readOnlyHint, the description discloses the caveats that actually affect interpretation: future-dated moves (mostly planned loan ends) are excluded unless planned=true, fee_eur is frequently null meaning unknown rather than zero, and profiles are re-read every 30 days so the newest moves can be absent. These are exactly the data-quality signals an agent needs and none are derivable from the annotations.

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?

Content is front-loaded with what is returned before filters and caveats, and nearly every clause carries information (null-fee semantics, date cutoff, refresh lag). The single dense paragraph is slightly run-on rather than wasteful.

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 eight optional parameters, no output schema, and no required fields, the description does the heavy lifting by enumerating returned fields and flagging freshness and null-fee caveats. The response envelope (list vs. object, total counts) remains unstated, which is the main residual gap.

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%, so the schema already defines sort, season, window, team_id, direction, league_id and planned. The description largely restates these (league filtering by current teams, window definitions, planned semantics) without adding syntax, defaults, or edge cases the schema lacks; baseline 3 is appropriate.

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 enumerates exactly what a record contains (player, from/to team, date, season, window, type, fee_eur), so an agent knows precisely what comes back. It does not explicitly contrast itself with any sibling, but no sibling in the catalog covers soccer transfers, so the risk of confusion is low.

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 rather than stated: it explains how to combine team_id with direction, and that sorting by fee surfaces 'the biggest moves'. There is no explicit when-to-use/when-not guidance and no named alternative tool for related needs (e.g., player or team lookups), so selection must be inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources