Skip to main content
Glama

renef_mem_scan

Scans Android process memory for a hex byte pattern and supports module-scoped Lua Memory.search with ?? wildcards; omit module for full-process compact-hex scans.

Instructions

Scan memory for a hex pattern. Prefer module="libfoo.so": it uses Lua Memory.search and supports spaces and ?? wildcards (e.g. "CA FE ?? BE"). Without module, the upstream full-process scan is used: compact hex only and it can exceed the server's ~10s response cap (an error will say 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": {
      "pattern": "<pattern>"
    },
    "name": "renef_mem_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
moduleNo
patternYes

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 full burden and does well: it discloses the two different backends (Lua Memory.search vs upstream full-process scan), the timeout ceiling and that failures surface as an explicit error. It omits privilege/attach requirements, which matters for a memory scanner.

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?

Three front-loaded sentences, recommendation first, then caveats; no filler. Slightly dense clause structure but every sentence adds distinct 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?

Return values are covered by the output schema, and the description supplies the syntax rules, backend choice and failure mode an agent needs. Missing only environment prerequisites (attached process, permissions) for a two-parameter scan tool.

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 explains that 'module' selects the search backend and takes a library name like libfoo.so, and that 'pattern' accepts spaced/?? wildcard syntax only in module mode but must be compact hex otherwise. The one gap is that omitting module (the empty default) is only implied, not stated outright.

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 ('Scan memory for a hex pattern') that clearly separates it from siblings like renef_mem_read, renef_mem_write and renef_mem_patch, which operate on known addresses rather than searching by pattern.

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 explicit parameter-level guidance ('Prefer module="libfoo.so"') and explains the tradeoff of omitting it (full-process scan, hex-only, ~10s cap risk). It does not name sibling alternatives, but the when-to-use-which-mode guidance is concrete and actionable.

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