Skip to main content
Glama

read_memory

Read memory contents from a target device by specifying address, length, access width, and access class. Returns a hex dump for debugging.

Instructions

Read memory from the target at a given address.

Args: address: Memory address as hex string (e.g., "0x80000000") or symbol name (e.g., "main") length: Number of bytes to read width: Access width in bits — 8, 16, 32, or 64 (default: 32) access: Access class prefix (e.g., "D:" for data, "P:" for program). Empty = default.

Returns: Hex dump of memory contents

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
widthNo
accessNo
lengthYes
addressYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided; description carries full burden. It mentions it returns a hex dump but lacks details on side effects, read-only guarantee, or error behavior.

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 concise with no wasted words, uses a clear parameter list format, and front-loads the 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?

Covers core functionality and parameters, but lacks context about when to use versus siblings and does not mention potential errors or behavior.

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

Parameters5/5

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

The description explains each parameter in detail (address as hex or symbol, length in bytes, width options with default, access class prefix) adding significant value beyond the schema with 0% description coverage.

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 clearly states it reads memory at an address with verb 'Read' and resource 'memory'. It is specific, but does not differentiate from sibling tools like read_memory_cached or read_memory_physical.

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?

No guidance on when to use this tool vs alternatives. The description only explains parameters, not usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/YangPan2020/debugforge'

If you have feedback or need assistance with the MCP directory API, please join our Discord server