Crawlora MCP

sofascore_team_transfers

Read-only

Returns a SofaScore team's recent incoming and outgoing transfers with player, clubs, date, fee and numeric type code. Use it for a club's current transfer activity by team id. Empty lists are valid for a quiet window, while not found means SofaScore has no transfer record (seen for ice hockey and baseball teams); type_code values are SofaScore's own opaque codes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	Required. Numeric SofaScore team id, e.g. 2817.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 7, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only cover readOnly/openWorld, so the edge-case detail here is genuinely additive: empty results are valid rather than an error, not-found has a known sport-specific cause, and type_code values are opaque SofaScore codes the agent should not interpret. That is exactly the context needed to avoid misreading the response.

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?

Three dense sentences, front-loaded with the core purpose and followed by usage and edge cases in descending order of importance. Nothing is padded or repeated from the schema.

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?

An output schema exists, so return values need not be described. Combined with annotations, the description covers purpose, invocation, ambiguity handling and sentinel semantics, leaving no practical gap for calling this one-parameter, read-only 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?

Schema coverage is 100% and the single 'id' parameter is fully documented in the schema ('Numeric SofaScore team id, e.g. 2817'). The description only echoes 'by team id' with no added format or lookup guidance, so baseline 3 applies.

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 ('Returns a SofaScore team's recent incoming and outgoing transfers') and enumerates the returned fields (player, clubs, date, fee, type code). The scoping word 'team's' implicitly separates it from sofascore_player_transfers without the agent needing to open either 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 says when to use it ('for a club's current transfer activity by team id') and clarifies the two ambiguous outcomes (empty list = valid quiet window; not found = no transfer record for that sport). It never names an alternative tool or a when-not condition, so it stops short of a 5.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.