Skip to main content
Glama

renef_load_script

Loads a Lua script file from the MCP host and executes it in the target Android process, enabling scripted instrumentation and automation through Renef.

Instructions

Load a Lua script file from the MCP host machine and run it in the target.

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": {
      "path": "<path>"
    },
    "name": "renef_load_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden and does not meet it: it never says whether loading executes immediately and unrecoverably, whether the script persists after return, what permissions or session state are required, or how file-not-found errors surface. The phrase 'run it in the target' implies arbitrary code execution in a penetration-testing context, which warrants an explicit warning about irreversibility and scope.

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

Conciseness4/5

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

A single front-loaded sentence with no filler; the host-versus-target distinction is placed prominently. Nothing is wasted, though there is also very little there.

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?

An output schema exists, so return values need not be explained, and a one-parameter tool is simple. But a code-loading/execution tool with zero annotations and zero schema descriptions needs the description to cover session prerequisites, execution side effects, and error behavior, and it covers none of these.

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 0% for the single 'path' parameter, so the description must compensate, and it does provide one genuinely important clarification: the file is read from the MCP host machine, not the target. It still leaves the path format open (absolute vs relative, .lua extension requirement, sandbox root), which is a real gap for a 100%-undocumented parameter.

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 a specific verb and resource combination ('Load a Lua script file ... and run it in the target'), which separates it from listing/reading script tools like renef_get_script or renef_list_scripts. It stops short of naming the sibling it is not (e.g. renef_exec for inline code), so an agent must still infer the boundary itself.

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?

There is no when-to-use guidance, no prerequisite disclosure (does a session need to be attached first via renef_attach?), and no mention of alternatives such as renef_exec or renef_get_script. The only signal is implicit: use it when you have a Lua file on the host.

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