Skip to main content
Glama
Sign In
FC 26 MCP

FC 26 MCP

by INSANE0777
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

le_release_player

Remove a player from your squad by releasing them to free agents. Provide player ID or name.

Instructions

Release a player to free agents.

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_release_player"
  }
}

Input Schema

NameRequiredDescriptionDefault
playerNoPlayer name (if ID not provided).
playeridNoPlayer ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.29

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description fails to disclose behavioral traits. It does not state whether the action is irreversible, requires permissions, or affects contracts. 'Release' implies a permanent change but lacks detail.

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 concise sentence with no fluff. However, it could be slightly longer to include necessary usage notes without being verbose.

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?

The tool is simple but lacks important context. No output schema, no annotation, and the description does not explain the effect of releasing a player (e.g., goes to free agents pool, contract termination). The optional parameters may cause confusion.

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 baseline is 3. The description adds no additional meaning to parameters. It does not clarify that at least one parameter (player name or ID) is likely required, though schema lists both as optional.

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 'Release a player to free agents' clearly states the verb 'release' and the resource 'player to free agents'. It distinguishes from sibling tools like le_loan_player (loan) and le_transfer_player (transfer).

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 like le_transfer_player or le_remove_from_lists. The description does not mention prerequisites or context for release.

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