Skip to main content
Glama

renef_mem_write

Write raw bytes to a target memory address using a hex string. Specify addr and hex_bytes to patch process memory during Android instrumentation.

Instructions

Write raw bytes to target memory. hex_bytes: hex string, spaces allowed, e.g. "1F 20 03 D5".

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>",
      "hex_bytes": "<hex_bytes>"
    },
    "name": "renef_mem_write"
  }
}

Input Schema

NameRequiredDescriptionDefault
addrYes
hex_bytesYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosure for a mutation operation. It explains the hex-byte format but does not state that this overwrites target memory, what permissions or attach state are required, how failures behave, or what the return value indicates.

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?

The description is two short sentences with no wasted wording. The core action is front-loaded and the format example is immediately useful.

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?

The tool is a destructive memory write with no annotations and an undocumented address parameter. Although an output schema exists and hex formatting is covered, the definition omits address semantics, attach requirements, and safety context that an agent needs before invoking it.

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 for both parameters. It does explain hex_bytes well, including spaces and an example, but addr is left completely unexplained even though address format is critical for a memory-write tool.

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 gives a specific verb and resource: "Write raw bytes to target memory." It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as renef_mem_write_value or renef_mem_patch, leaving the agent to infer the difference from "raw bytes" alone.

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 guidance on when to use this tool rather than writing a typed value or patching memory, nor any mention of prerequisites such as an attached process or writable memory. The usage context is only indirectly implied by the function itself.

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