Skip to main content
Glama

renef_mem_read_string

Reads a NUL-terminated C string from an Android process's target memory address, optionally limiting the maximum bytes read.

Instructions

Read a NUL-terminated C string from target memory.

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

Input Schema

NameRequiredDescriptionDefault
addrYes
max_lenNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and does not meet it. It says nothing about what happens when no NUL is found within max_len (truncation? error?), what occurs on an unmapped or invalid address, whether permissions or an attached session are required, or how the returned string is encoded.

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?

A single front-loaded sentence with zero padding or redundancy. The tradeoff is under-specification rather than verbosity, but as a piece of prose it is tight and well-structured.

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

Completeness2/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-format explanation is not required, but the definition still leaves out the operational essentials for a two-parameter memory read with 0% schema coverage. Nothing tells the agent how the read boundary or failure modes behave.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across two parameters, so the description must compensate and does not. It never explains that 'addr' is a memory address literal or that 'max_len' bounds the read and defaults to 256, which is exactly the truncation behavior an agent needs to reason about.

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?

States a specific verb (read) and resource (NUL-terminated C string) in target memory, which is meaningfully narrower than the sibling renef_mem_read (raw bytes) or renef_mem_read_value (typed value). It does not name those siblings, so the differentiation is implicit rather than explicit.

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?

No when-to-use or when-not-to-use guidance is given, and no prerequisite (e.g. an active attach) is stated. The user must infer from 'NUL-terminated C string' that this tool is the one to pick for string data rather than for raw or numeric memory.

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