FC 26 MCP

Overview Schema Source Related Servers Discussions Admin

le_execute_lua

Execute custom Lua scripts to control and manage career mode in EA SPORTS FC 26. Use with caution due to powerful capabilities.

Instructions

Run custom Lua (powerful, use carefully).

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": {
      "code": "<code>"
    },
    "name": "le_execute_lua"
  }
}

Input Schema

Name	Required	Description	Default
`code`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.29Jul 14, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. It warns the tool is 'powerful' and to 'use carefully', but does not disclose side effects, required permissions, or return behavior, which is critical for a code execution tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short (5 words), which might be considered concise, but it omits essential details. For a powerful tool, more information is needed.

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

Completeness1/5

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

Given the tool's complexity (code execution), lack of annotations, output schema, and parameter descriptions, the description is severely incomplete. It should specify scope, available libraries, return values, and security considerations.

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

Parameters1/5

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

Schema coverage is 0% and the description provides no information about the 'code' parameter beyond the schema's type (string). The description adds no semantic value.

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 states 'Run custom Lua', which clearly indicates the action (run) and resource (Lua code). It distinguishes from sibling tools that are specific database or player operations, as this is a general code execution tool.

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 explicit guidance on when to use or not use this tool versus alternatives. The warning 'use carefully' implies caution but does not provide context-specific recommendations.

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