Skip to main content
Glama

renef_module_find

Finds the base address of a loaded Android module by name, such as libc.so, so you can resolve memory offsets for hooking or inspection.

Instructions

Get the base address of a loaded module, e.g. renef_module_find("libc.so").

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure and does not meet it. It does not state whether a process must be attached first, what happens if the module is not loaded (error vs. null/zero), or whether the lookup is a safe read-only operation — all of which matter for a memory-inspection tool in this suite.

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?

One compact sentence with the purpose front-loaded and an example appended. Nothing is wasted, though the example could have been paired with a one-clause caveat about preconditions at no real cost.

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

Completeness5/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 required, and with only one required string parameter the surface area is small. The remaining omission — attach preconditions and not-found behavior — is a transparency issue already counted elsewhere rather than a structural gap.

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%, so the description must compensate for the single 'name' parameter. The example 'libc.so' does convey that the value is a module file name rather than a path or handle, which is real added meaning, but it leaves open whether full paths, sonames, or case-sensitivity variations are accepted.

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 names a specific verb and resource — 'get the base address of a loaded module' — which is distinct from sibling operations like renef_module_list (enumerate) or renef_module_symbols (resolve symbols). The inline example further pins down the concept. It does not explicitly contrast itself with those siblings, so it falls short of a 5.

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 example call 'renef_module_find("libc.so")' implicitly demonstrates the intended usage context, but there is no explicit statement of when to use this versus renef_module_list or renef_module_symbols, and no mention of preconditions such as requiring an attached process. Usage is inferable rather than stated.

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