Skip to main content
Glama
AstralVoidZ
by AstralVoidZ

ppsspp_write_memory

Destructive

Write u8, u16, u32, or raw byte values to a PSP emulator memory address using an active session ID. Use force mode to modify protected kernel or code ranges.

Instructions

PURPOSE: Write u8/u16/u32 or raw bytes to memory.

USAGE: session_id + address ('0x' hex) + data + format ('u8'|'u16'|'u32'|'bytes'; bytes accepts hex or base64).

BEHAVIOR: DESTRUCTIVE. Protected ranges (kernel, top.prx code) need force=true (PROTECTED_ADDRESS).

RETURNS: {address, format, bytes_written, value, text}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesValue to write, as a string. For format='u8'/'u16'/'u32', a hex string (e.g. '0x00000001') or decimal string (e.g. '1'). For format='bytes', a hex string (e.g. 'AABBCCDD') or base64 string.
forceNoSet to True to write to protected code-section addresses (kernel memory < 0x08800000 or top.prx code section 0x08804000-0x08D34000). Writing to these ranges without force=True raises ToolError to prevent accidental crashes.
formatNoWrite format. 'u32' (default) writes a 32-bit int. 'u8'/'u16' write byte/halfword granules (byte patches). 'bytes' writes raw bytes (data is hex-decoded).u32
addressYesTarget address, as a hex string (e.g. '0x08804000').
session_idYesActive session ID.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesUnified text representation: 'Wrote 0xVAL → 0xADDR' for u32, 'Wrote N bytes → 0xADDR' for bytes.
valueYesFor format='u32', the value written as hex string (e.g. '0x00000001'); None for 'bytes'.
formatYes'u32' or 'bytes'.
addressYesTarget address, hex string (e.g. '0x08804000').
bytes_writtenYesNumber of bytes written.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

The description explicitly labels the operation 'DESTRUCTIVE' and discloses that protected ranges (kernel, top.prx code) require force=true to avoid accidental crashes. This adds behavioral context beyond the annotations by describing the protected-range constraint and the consequence of not using force.

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 tightly organized into PURPOSE, USAGE, BEHAVIOR, and RETURNS sections. Every sentence carries meaningful information, with the destructive behavior and key constraint front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers purpose, invocation requirements, behavioral risks, protected-range handling, and return shape. Combined with a rich schema and output schema, an agent has sufficient information to call the tool 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 description coverage is 100%, and the schema already documents data, format, address, force, and session_id in detail. The description's usage line mostly restates this information, adding little beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action and resource: 'Write u8/u16/u32 or raw bytes to memory.' It clearly distinguishes from sibling tools like ppsspp_write_register and ppsspp_read_memory by specifying the resource (memory) and accepted formats.

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 an invocation formula ('session_id + address + data + format'), but no guidance on when to choose this tool over alternatives such as ppsspp_write_register or ppsspp_assemble. The only conditional guidance ('protected ranges ... need force=true') is about a parameter, not about tool selection.

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