Skip to main content
Glama

renef_get_script

Returns the Lua source code of a bundled Renef script by name, so you can inspect or reuse it before running it on a rooted Android process.

Instructions

Return the Lua source of a bundled script (see renef_list_scripts), e.g. renef_get_script("flutter_ssl").

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. 'Return the Lua source' implies a non-mutating read, which is useful, but it says nothing about behavior for an unknown script name, whether names are case-sensitive, or whether the returned source is raw text or wrapped. For a simple read tool this is acceptable but not complete.

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?

Two short lines, front-loaded with the verb and resource, followed immediately by discovery pointer and example. No filler whatsoever.

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

Completeness4/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-value description is not required, and the tool is a one-parameter read. The definition covers purpose, discovery path, and an example; only error behavior for invalid names is left unaddressed.

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% and the single parameter is a bare 'name' string with no description. The description partially compensates by naming renef_list_scripts as the source of valid names and giving a concrete example value ('flutter_ssl'), which is more than the schema offers. It still omits any naming convention or format detail.

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?

States a specific verb and resource: 'Return the Lua source of a bundled script.' The parenthetical pointer to renef_list_scripts and the concrete example make the object of the operation unambiguous. It does not explicitly distinguish itself from renef_load_script, so a sibling differentiation gap remains.

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?

The reference to renef_list_scripts implies the correct workflow (discover names, then fetch source), which is genuine usage guidance. However, it gives no when-not guidance and does not clarify how this differs from renef_load_script, which an agent could easily confuse with it.

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