Skip to main content
Glama

renef_list_scripts

Lists bundled Renef Lua example scripts for hook demos, tracing, and SSL unpinning bypasses, so you can select one to load or execute.

Instructions

List the bundled Renef Lua example scripts (hook demos, tracing, flutter_ssl / ssl_unpin / root_bypass bypasses). Load one with renef_get_script

  • renef_load_script, or paste into renef_exec.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "renef_list_scripts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/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 behavioral burden; it does convey that these are bundled/example (i.e. local, static) scripts and what kinds exist, which implies a safe read. It does not state whether a device or session connection is required, whether the list is static or user-extendable, or any access constraints.

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 tight sentences: the first defines the resource and its contents, the second routes the agent to the next action. No filler, and the purpose is front-loaded.

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 and there are no parameters, so return-value explanation is unnecessary. The description covers purpose and follow-up actions well; the only real gap is whether listing requires an attached target, which slightly limits completeness for a session-based toolkit.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. No parameter guidance is needed or missing.

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?

States a specific verb and resource ('List the bundled Renef Lua example scripts') and even enumerates the categories of scripts included (hook demos, tracing, flutter_ssl/ssl_unpin/root_bypass). It distinguishes itself cleanly from renef_get_script and renef_exec by naming them as follow-on steps rather than overlapping actions.

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?

Gives a clear workflow: discover here, then 'Load one with renef_get_script + renef_load_script, or paste into renef_exec.' That tells an agent what comes next and which sibling to use for each path. It stops short of explicit exclusions (e.g. when not to use this versus listing device-side scripts), which keeps it at 4.

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