Skip to main content
Glama

renef_list_hooks

Lists active native hooks in the target Android process so you can inspect what is currently intercepted before modifying or removing hooks.

Instructions

List active native hooks in the target process. Upstream's registry is native-only: Java hooks (renef_hook_java) do not appear here and cannot be removed by renef_unhook; they are restored when the agent connection closes, i.e. on the next attach/spawn.

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_hooks"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does substantial work: it discloses that the registry is native-only, that Java hooks are not removable via renef_unhook, and that they are restored when the agent connection closes on the next attach/spawn. That lifecycle detail is non-obvious and directly affects agent decisions; missing only read-only framing and whether an attach is required.

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?

Front-loaded with the operation, then the two caveats, with no filler. The final clause 'i.e. on the next attach/spawn' is slightly compressed and takes a second read, but every sentence contributes decision-relevant information.

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 explanation is not owed, and the description covers the main confusion risk (missing Java hooks). It leaves unstated whether the agent must be attached before listing, which is the one operational precondition an agent might need.

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 and the baseline of 4 applies. The description correctly does not waste space restating an empty schema.

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 active native hooks') plus an explicit scope ('in the target process'), and immediately draws the boundary against the Java path by naming renef_hook_java. An agent can distinguish this from the hooking and listing siblings without opening the schema.

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?

The exclusion rule is stated clearly: Java hooks do not appear in this registry, so an agent knows not to use this tool to verify a Java hook. It stops short of explicitly saying where to go for Java hook state, and gives no guidance on prerequisites such as being attached first.

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