FC 26 MCP

by INSANE0777

Overview Schema Source Related Servers Discussions Admin

Python

Local

le_add_to_loan_list

Add a player to the loan list by providing their ID or name, enabling career mode loan management.

Instructions

Add a player to the loan 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_loan_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 present, and the description does not disclose behavioral traits such as required permissions, side effects (e.g., overwriting existing entries), or return value. Minimal information for a mutation operation.

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?

Description is a single sentence with no wasted words. It is front-loaded but could be expanded without harming 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?

Given no output schema, no annotations, and moderate parameter count, the description is insufficient. It does not explain required inputs, behavior on invalid data, or success criteria.

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 67% (two of three parameters have descriptions). The description adds no extra meaning beyond the schema; it does not clarify how parameters relate or which are preferred.

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 clearly states the action (add) and resource (player to loan list). However, it does not distinguish this tool from sibling tools like 'le_add_to_transfer_list' or 'le_remove_from_lists', missing an opportunity to differentiate.

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 is provided on when to use this tool versus alternatives, no prerequisites, conditions, or exclusions are mentioned.

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