Skip to main content
Glama

renef_mem_read

Reads bytes from a target Android process's memory and returns a hexdump, with addresses in decimal or 0x-hex and reads capped at 4096 bytes.

Instructions

Read bytes from target memory and return a hexdump. addr accepts decimal or 0x-hex. size is capped at 4096 bytes.

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": {
      "addr": "<addr>"
    },
    "name": "renef_mem_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
addrYes
sizeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full disclosure burden. It does add real value by disclosing the 4096-byte cap and the hexdump output shape, but it omits whether oversize requests truncate or error, whether an attach/session is required, and what happens on invalid addresses.

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?

Three short sentences, each front-loading a distinct fact: what it does, the address format, the size limit. No filler and no restatement of the tool name.

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

Completeness3/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 detail is not required, and the description covers both parameters. However, for a memory-inspection tool in a suite that includes renef_attach, the missing statement of session/attachment prerequisites and oversize-handling behavior leaves a meaningful gap.

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 description coverage is 0%, so the description must compensate, and it largely does: it defines the accepted addr syntax (decimal or 0x-hex) and the size ceiling of 4096 bytes. It does not clarify unit/behavior at the boundary (error vs. truncation) or restate the default of 64, which the schema already supplies.

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 uses a specific verb plus resource ('Read bytes from target memory') and states the return format ('return a hexdump'), which is far more informative than the bare name. It stops short of distinguishing this from siblings such as renef_mem_read_string or renef_mem_read_value, so an agent gets a clear purpose but no sibling routing.

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?

Usage is only implied: 'read bytes ... return a hexdump' hints at raw-byte access, which suggests the string/value variants are for typed reads. There is no explicit 'use this when' or 'prefer X for Y' guidance, and no mention of prerequisites such as being attached to a target process.

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