Skip to main content
Glama

pine_write32

Write a 32-bit value to emulated memory at a 4-byte aligned address for PlayStation emulation.

Instructions

Write a 32-bit value (LE) to emulated RAM. Address must be 4-byte aligned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesMemory address (4-byte aligned)
valueYes

Implementation Reference

  • Tool definition/input schema for pine_write32: requires address (integer) and value (integer, minimum 0), writes a 32-bit little-endian value to 4-byte aligned RAM.
    {
      name: "pine_write32",
      description: "Write a 32-bit value (LE) to emulated RAM. Address must be 4-byte aligned.",
      inputSchema: {
        type: "object",
        required: ["address", "value"],
        properties: {
          address: { type: "integer", description: "Memory address (4-byte aligned)" },
          value:   { type: "integer", minimum: 0 },
        },
      },
  • The request handler for pine_write32: calls pine.write32(addr(), p.value as number) and returns a confirmation string with the hex value and address.
    case "pine_write32": {
      await pine.write32(addr(), p.value as number);
      return ok(`Wrote ${fmtHex(p.value as number)} → ${addrHex(addr())}`);
    }
  • The PineClient.write32 method: assembles an 8-byte buffer (4-byte address LE + 4-byte value LE) and sends it via the PINE protocol with opcode Write32 (0x06).
    async write32(addr: number, val: number): Promise<void> {
      const args = Buffer.alloc(8);
      args.writeUInt32LE(addr, 0);
      args.writeUInt32LE(val, 4);
      await this.call(Op.Write32, args);
    }
  • Opcode constant Write32 = 0x06, used by the PINE protocol to identify a 32-bit write operation.
    Write16:      0x05,
    Write32:      0x06,
Behavior2/5

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

No annotations provided. Description mentions 32-bit LE and alignment but does not disclose behavior on misalignment, error handling, or whether values are truncated beyond 32 bits.

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?

One sentence, 11 words, no wasted text. Front-loads essential action and constraint.

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

Completeness4/5

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

Given no output schema and simple write operation, the description covers action, data type, and alignment constraint. Lacks mention of effect on state or any side effects.

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 50%; address parameter schema reiterates alignment. Description adds '32-bit LE' context for value, but does not specify maximum value beyond schema minimum 0.

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?

Clear verb 'Write', specific resource '32-bit value (LE) to emulated RAM', and distinguishes from siblings like pine_read32 and pine_write64/write8.

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 versus alternatives like pine_write16 or pine_write64. Does not mention differences in precision or use cases.

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/dmang-dev/mcp-pine'

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