Skip to main content
Glama

renef_exec

Execute Lua code in a target Android process to inspect or modify runtime state, returning print() output for immediate feedback.

Instructions

Execute Lua code in the target process and return print() output. Main tool. Examples: "print(Module.list())", "print(Memory.readString(args[0]))". Multi-line Lua is fine. See resource renef://docs/lua-api for the full API.

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": {
      "lua": "<lua>"
    },
    "name": "renef_exec"
  }
}

Input Schema

NameRequiredDescriptionDefault
luaYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the core behavior—executing arbitrary Lua in the target process and returning print() output—and notes that multi-line code is fine. However, it omits critical behavioral context for an arbitrary code execution tool: whether it can mutate memory or hooks, required permissions or attach state, sandboxing, error behavior, and side-effect risks.

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?

The description is four short sentences, front-loaded with the core action, followed by concrete examples and a documentation pointer. Every sentence adds value; there is no filler or repetition.

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?

For a high-complexity arbitrary Lua execution tool with no annotations, the definition covers the basic action, output channel, and multi-line usage. It leaves important gaps around prerequisites, safety implications, sandboxing, and when to choose specialized siblings instead. The existing output schema reduces the need to explain return values, but behavioral completeness is still partial.

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 0%, so the description must compensate for the single 'lua' parameter. It adds useful meaning through examples and the note that multi-line Lua is accepted, and the example 'args[0]' hints at an implicit args variable. It still does not explicitly describe the parameter's format, available runtime globals, or error/return handling beyond print output.

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 states a specific verb and resource: execute Lua code in the target process, returning print() output. The examples and the label 'Main tool' make clear that this is the general-purpose scripting entry point, distinguishable from specialized siblings such as renef_mem_read or renef_hook_native.

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

Usage Guidelines4/5

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

It gives clear usage context by calling itself the 'Main tool' and providing concrete example invocations, plus a pointer to the Lua API docs. It does not explicitly state when to prefer this over targeted siblings like renef_mem_read or when not to use it for simple operations, so it falls short of full alternative guidance.

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