Skip to main content
Glama

Read Bytes

read_bytes
Idempotent

Reads exact bytes from a provider-normalized virtual address for reverse engineering, returning explicit incomplete reads and typed capability errors when a provider API is unsupported.

Instructions

Read analyzed bytes from one provider-normalized virtual address. The hexadecimal payload reports the exact returned length; incomplete reads remain explicit and unsupported provider APIs return typed capability unavailability.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "length": 16,
      "address": "0x1000"
    },
    "name": "read_bytes"
  }
}

Input Schema

NameRequiredDescriptionDefault
lengthNo
addressYesA provider-normalized address; default memory uses 0x-prefixed hexadecimal
documentNoThe active target's provider document name; use open_binary to switch targets

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover idempotency and non-destructiveness, and the description adds genuine beyond-schema behavior: a hexadecimal payload that reports exact returned length, explicit partial/incomplete reads, and typed capability-unavailability errors for unsupported providers. That is real error-and-output semantics an agent needs. Note the mild tension with readOnlyHint=false, since the wording frames this as a pure read, though reading memory plausibly requires session/analysis state so it is not a direct contradiction.

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 sentences, front-loaded with the action and address scope before the output/error behavior. Dense but purposeful; "typed capability unavailability" is jargon-heavy phrasing that costs a little readability without wasting much space.

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?

With no output schema, the description correctly spends its words on return shape (hex payload, exact length, partial reads) and error behavior, which is the right allocation. However, it leaves the length and document parameters unaddressed and does not say what happens when the address is unmapped or how much analysis must precede a read, so a few practical gaps remain.

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?

With 67% schema coverage, the baseline is 3. The description clarifies the address parameter ("provider-normalized virtual address") but says nothing about the length parameter's semantics or the document parameter, both of which the schema handles only partially. It adds meaning for the required parameter and nothing for the rest.

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 names a specific verb and resource ("Read analyzed bytes") and scopes it to "one provider-normalized virtual address," which is enough for an agent to know this is a memory-read primitive rather than a logcat/setting reader from the sibling list. It stops short of explicitly distinguishing itself from adjacent address/file-offset helpers, but the core action is unambiguous.

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?

Usage is implied rather than stated: reading bytes at an address in the currently open target. There is no explicit 'use this when X, use Y instead' routing, and the schema's own note ("use open_binary to switch targets") is the only pointer to related tools. Adequate but leaves the agent to infer the conditions.

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

Deploy Server

Other Tools