Execute arbitrary Lua code inside a running LÖVE2D game to modify behavior in real time or inspect internals.
Execute arbitrary Lua code in the game context
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | The Lua code to execute |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden for a tool that executes arbitrary code. It says nothing about sandboxing, permissions, side effects on game state, whether execution is synchronous, how errors or return values surface, or whether results are returned at all — a major gap for such a powerful operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no wasted words; it is efficient and readable. It is arguably under-specified rather than over-long, but conciseness itself is good.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a code-execution tool with no annotations and no output schema, the description is far too thin. It omits what the code can access, what happens on error, and whether any value is returned, leaving the agent unable to predict the outcome of a call.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Only one parameter exists and schema description coverage is 100%, so the schema already documents 'code' fully. The description adds no syntax, format, or constraint details beyond what the schema provides, making the baseline 3 appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Execute) and resource (arbitrary Lua code) with the execution scope ('in the game context'), which lets an agent distinguish it from siblings like list_lua_files and reload_code. However, it does not explicitly contrast itself with those siblings, so it falls short of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to reach for run_lua versus list_lua_files, reload_code, or send_input, nor any prerequisites or exclusions. The agent must infer usage entirely from the name and one-line description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.