FC 26 MCP

by INSANE0777

Overview Schema Source Related Servers Discussions Admin

Python

Local

le_add_to_transfer_list

Add a player to the transfer list by specifying their Player ID or name to manage career mode transfers.

Instructions

Add a player to the transfer list.

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": "le_add_to_transfer_list"
  }
}

Input Schema

Name	Required	Description
`player`	No	Player name (if ID not provided).
`teamid`	No
`playerid`	No	Player ID.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.29Jul 14, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as side effects, authentication needs, or whether adding an existing player overwrites or duplicates.

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?

The description is a single clear sentence, front-loaded with the essential purpose. However, it could be slightly expanded to improve completeness without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and minimal parameter descriptions, important context is missing: whether duplicates are allowed, what the return value is, and if the player must already belong to the club.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 67% coverage, but the description adds no additional meaning for the parameters. It fails to explain the role of 'teamid' (which lacks a schema description) or the relationship between 'player', 'playerid', and 'teamid'.

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 'Add a player to the transfer list' clearly states the verb (Add), resource (player), and target (transfer list), distinguishing it from sibling tools like 'le_add_to_loan_list' or 'le_is_transfer_listed'.

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?

No guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The description simply states the action without context.

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