Skip to main content
Glama

renef_mem_write_value

Writes an integer to a target memory address with selectable 1-, 2-, 4-, or 8-byte size, enabling precise memory modification in Android processes.

Instructions

Write an integer to target memory. size: 1, 2, 4 or 8 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>",
      "value": "<value>"
    },
    "name": "renef_mem_write_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
addrYes
sizeNo
valueYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the writable widths (1/2/4/8 bytes), but says nothing about this being an irreversible memory mutation, required attachment state, endianness, failure modes on unmapped addresses, or whether writes are verified. For a destructive memory-write primitive that is a substantial gap.

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, front-loaded sentences with no filler; the core action comes first and the constraint second. It is efficient, though its brevity reflects under-specification rather than optimal density.

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?

For a 3-parameter memory-mutation tool with no annotations and 0% schema coverage, the definition is too thin. An output schema exists so return values needn't be explained, but the address format and the prerequisite that a process be attached are missing and are essential to calling it correctly.

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%, so the description must compensate. It usefully enumerates the allowed 'size' values (1, 2, 4, 8) beyond the schema's bare default of 4, but 'addr' format (hex string? module+offset? absolute?) and 'value' range/signedness are completely undocumented.

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 and resource ('Write an integer to target memory'), which is clearly narrower than the sibling renef_mem_write (byte-level) and renef_mem_patch. It does not explicitly name or contrast with those siblings, so the differentiation must be inferred from the word 'integer'.

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 when-to-use guidance at all: nothing tells the agent when to prefer this over renef_mem_write, renef_mem_patch, or renef_mem_scan, nor what preconditions exist (e.g. an attached process via renef_attach). The only guidance is the implicit size constraint.

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