Skip to main content
Glama

emu_read_mem

Read up to 4096 bytes from emulated memory in hex or ASCII to inspect memory before or after a run.

Instructions

Read up to 4096 bytes from emulated memory.

fmt is "hex" or "ascii". Use to inspect memory after/before a run.

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>",
      "length": "<length>"
    },
    "name": "emu_read_mem"
  }
}

Input Schema

NameRequiredDescriptionDefault
fmtNohex
addrYes
lengthYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 behavioral burden, and it does disclose one real constraint: the 4096-byte maximum per read. It says nothing about out-of-range addresses, whether reads can fail on unmapped memory, alignment requirements, or the width of the address space, so the mutation-free safety profile and error behavior remain unstated.

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, front-loaded with the core action and cap, and both sentences earn their place. The backticked fmt note reads as a parenthetical but does not obscure the front-loaded purpose.

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 no explanation and the tool is not expected to describe its response. The remaining gap is significant for a memory accessor: address semantics and read-failure behavior are undocumented, which is exactly what an agent needs to call this safely.

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%, so the description must compensate, and it partially does: it declares the accepted values of fmt ("hex" or "ascii") even though the schema defines no enum, and it implies the length cap. The addr parameter, the most error-prone field, is left entirely unexplained, including whether it is a hex string, a decimal integer, or what address space it indexes into.

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 up to 4096 bytes from emulated memory" gives a specific verb, resource, and an explicit size cap, so the agent immediately knows this is a bounded memory read. It does not explicitly differentiate itself from emu_write_mem or emu_trace, though the read verb makes the distinction reasonably obvious.

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?

"Use to inspect memory after/before a run" supplies a timing context for when the tool is appropriate, which is genuine guidance beyond the name. However, it names no alternative and states no exclusions, so an agent still has to infer the boundary against emu_trace or emu_hook_call.

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