Skip to main content
Glama

gc_memory_write

Writes hexadecimal byte data to a specified address in an emulated GameCube instance's RAM, enabling direct memory modification during Dolphin emulation.

Instructions

Write bytes to the emulated GameCube RAM.

data is a hex string (e.g. "00010203"). address is a Dolphin emulated address. 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>",
      "data": "<data>"
    },
    "name": "gc_memory_write"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYes
addressYes
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 burden, and it does disclose two useful behavioral facts: the data encoding (hex string) and failure semantics ('fails gracefully if memory is not available'). It omits preconditions such as whether the emulator must be running, whether a valid address range is enforced, whether writes can partially succeed, and what the call returns.

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?

Three short sentences, front-loaded with the action and resource, followed by parameter detail and then failure behavior. No filler or restated name/title text; every sentence adds information.

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 mutation tool with no annotations and no output schema, the description covers the essentials of how to call it but not the surrounding context: the role of instance_id, the requirement that a Dolphin instance be attached, and the return/error shape are all absent. It is adequate but not complete.

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. It meaningfully clarifies two of three parameters: data is a hex string with a concrete example, and address is a Dolphin emulated address. instance_id is left completely unexplained, which is a real gap for a required parameter.

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 opens with a specific verb+resource pair: 'Write bytes to the emulated GameCube RAM.' That is unambiguous and lets an agent distinguish it from gc_memory_read. It does not explicitly name gc_memory_write_struct as the sibling alternative, so it stops short of a 5.

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 explicit when-to-use or when-not-to-use guidance, and no mention of the struct-based sibling that an agent would likely confuse this with. Usage is only implied by the tool name and the word 'bytes', leaving the raw-vs-struct choice to inference.

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