Skip to main content
Glama

gc_memory_read

Reads bytes from emulated GameCube RAM at a Dolphin address and returns them as a hex string, failing gracefully when memory is unavailable.

Instructions

Read bytes from the emulated GameCube RAM.

address is a Dolphin emulated address (e.g. 0x80000000 for the start of MEM1). Returns a hex string. Fails gracefully if memory is not available.

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": {
      "instance_id": "<instance_id>",
      "address": "<address>",
      "length": "<length>"
    },
    "name": "gc_memory_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
lengthYes
addressYes
instance_idYes

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 does useful work: it discloses the return type (hex string) and failure behavior ("Fails gracefully if memory is not available"). However, it says nothing about whether the target instance must be running, size limits on reads, or what a graceful failure looks like to the caller.

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?

Short and front-loaded: purpose first, then address format, return type, and error behavior. Slightly wasteful line-splitting but no filler sentences.

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?

For a 3-parameter tool with no output schema and no annotations, the description covers return format and failure mode reasonably well, but leaves the instance_id parameter and read-size constraints undocumented, which an agent needs in order to call it correctly.

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 coverage is 0%, so the description must compensate. It gives strong meaning for address (Dolphin emulated address with a concrete 0x80000000/MEM1 example), but instance_id is entirely unexplained and length is only hinted at by "read bytes" – two of three parameters remain ambiguous.

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: "Read bytes from the emulated GameCube RAM." This is clearly distinguishable from write siblings, though it never contrasts with the similarly named gc_memory_read_struct, so the raw-bytes vs structured distinction must be inferred from the name alone.

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 only implied by "read bytes" – there is no explicit statement of when to prefer this over gc_memory_read_struct or when it is inappropriate. No prerequisites or instance-selection guidance is given.

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