Skip to main content
Glama

renef_mem_read_value

Read integer values from target Android process memory with selectable 1, 2, 4, or 8-byte sizes and optional signed interpretation.

Instructions

Read an integer from target memory. size: 1, 2, 4 or 8 bytes (unsigned unless signed=true).

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

Input Schema

NameRequiredDescriptionDefault
addrYes
sizeNo
signedNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does establish that this is a non-mutating integer read and encodes the size/signedness semantics. It says nothing about failure modes (unmapped address, no attached target) or whether the read is bounds-checked, which matters for a memory-access tool.

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?

Two short sentences with no filler, and the core action is front-loaded before the parameter notes. It is slightly too terse for the topic — "target memory" is never grounded — but nothing is wasted.

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 values need not be explained, and the size/signed semantics are covered. For a 3-parameter memory-access tool with zero annotation coverage, the missing address format and missing attach prerequisite leave meaningful gaps.

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 description coverage is 0%, and the description compensates for size (allowed values 1/2/4/8) and signed (unsigned by default), which is genuinely useful. The required addr parameter gets no format guidance at all — hex string vs decimal, prefix conventions — leaving the most important argument ambiguous.

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?

"Read an integer from target memory" gives a specific verb and resource, and the word "integer" implicitly separates it from byte-oriented or string-oriented reads among the siblings. It stops short of naming renef_mem_read or renef_mem_read_string, so the differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance and no mention of the obvious alternative tools for reading memory. It also omits the prerequisite that a target must be attached (e.g., via renef_attach) before this call is meaningful.

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