Skip to main content
Glama

renef_unhook

Remove a specific Android hook by ID or clear all hooks to restore original method behavior during Renef instrumentation.

Instructions

Remove a hook by id (from renef_list_hooks), or "all" to remove every hook.

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

Input Schema

NameRequiredDescriptionDefault
hook_idYes

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 supplied, the description carries the full disclosure burden. It does disclose the destructive bulk scope of "all" ("remove every hook"), which is the key behavioral fact, but says nothing about reversibility, required attach/permission state, or what happens on an unknown id.

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?

One sentence, front-loaded with the verb and resource, with the id-source hint and the bulk option packed in without any redundant wording.

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?

For a single-parameter removal tool with an output schema, the description covers what is removed and the bulk case. Only edge-case behavior (invalid id, whether removal is undoable) is left implicit.

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?

Schema coverage is 0%, so the description must compensate, and it does: it establishes that hook_id is an id obtained from renef_list_hooks and that the literal string "all" is an accepted sentinel value. That sentinel is meaningful semantics the bare string schema does not convey.

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?

Specific verb ("Remove") plus resource ("hook"), with the identifier source named (renef_list_hooks). It is immediately distinguishable from the listing sibling and from the hook-creation siblings (renef_hook_generate, renef_hook_java, 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?

Tells the agent where valid ids come from (renef_list_hooks) and offers the "all" shortcut for bulk removal. It stops short of stating when not to use it (e.g. whether hooks must be detached or scripts reloaded first), but the usage context is clear.

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