FC 26 MCP

Overview Schema Source Related Servers Discussions Admin

le_set_player_morale

Set a player's morale level from 0 to 100 in FC 26 Career Mode. Specify the player by ID or name and the desired morale value.

Instructions

Set player morale (0-100). 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_morale"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.29Jul 14, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations provided; description only indicates mutation (set). Does not disclose side effects, idempotency, permissions, or what happens on invalid input beyond schema.

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?

Extremely concise: two sentences, front-loaded with action and scope. No wasted words.

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?

Minimal description for a mutation tool with no output schema. Lacks return value, error handling, prerequisite (player existence), and interaction with other morale mechanics.

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 already describes two of three parameters. Description adds no extra meaning beyond restating the valid range for 'value'. Baseline 3 due to moderate schema coverage.

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 verb 'Set', specific resource 'player morale', valid range '(0-100)', and scope 'Career Mode only'. Distinguishes from sibling tools like loans and transfers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implied usage for Career Mode, but no explicit when-to-use or alternatives. Lacks guidance on when not to use this tool over similar mutation tools.

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