Skip to main content
Glama
Sign In
FC 26 MCP

FC 26 MCP

by INSANE0777
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

le_set_player_fitness

Set a player's fitness level (5-95) in FC 26 Career Mode using player ID or name to manage fatigue and performance.

Instructions

Set player fitness (5-95). Career Mode only.

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": {
      "value": "<value>"
    },
    "name": "le_set_player_fitness"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.29

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. Only states it sets fitness with a range, but does not disclose behavior on invalid input, return value, or whether it is destructive. 'Career Mode only' is the only behavioral context.

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?

Single sentence with no redundancy. Every word carries information.

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

Completeness3/5

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

Covers range and mode constraint, but lacks details on parameter interactions (e.g., which takes priority when both player and playerid provided), validation behavior, and output. Could be more complete for a simple setter.

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 high (67%), so baseline is 3. Description does not add parameter details beyond what schema provides; it only repeats the range inline. No new semantic info.

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?

Clear action verb 'Set' with specific resource 'player fitness', valid range 5-95, and exclusive mode constraint 'Career Mode only'. Distinct from sibling tools which deal with other attributes or actions.

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?

Provides the 'Career Mode only' constraint but no guidance on when to use this tool vs siblings like le_set_player_form or le_set_player_morale. No mention of prerequisites or alternatives.

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