pet-tools-mcp

Overview Schema Source Related Servers Discussions Admin

pet_rom_disasm

Disassemble live memory in a Commodore PET emulator with ROM and session symbol annotations, accepting hex, decimal addresses, or symbol names like CHROUT.

Instructions

Disassemble live memory with ROM + session symbol annotations. start accepts $hex/0xhex/decimal or a symbol (e.g. CHROUT).

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": {
      "start": "<start>"
    },
    "name": "pet_rom_disasm"
  }
}

Input Schema

Name	Required	Description	Default
`start`	Yes
`length`	No
`session`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 11, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It implies a read-only disassembly operation but does not disclose whether it modifies state, requires an active session, or what the output format is. Key behavioral aspects like side effects and constraints are missing.

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 extremely concise: two sentences that clearly convey the tool's purpose and a critical parameter detail. Every sentence adds value with no redundancy or filler.

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

Completeness2/5

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

Given the tool has three parameters, no output schema, and no annotations, the description is too sparse. It omits explanations for two parameters and provides no information about return values or behavioral context. A more complete description is needed for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description must explain parameters beyond the schema. It only describes the 'start' parameter format, leaving 'length' (default 32) and 'session' (nullable string) unexplained. This is insufficient for a three-parameter tool.

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 clearly states the verb 'disassemble' and the resource 'live memory with ROM + session symbol annotations'. It distinguishes the tool from siblings like pet_mem_read (raw memory read) and pet_build (build) by specifying the annotation context.

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?

The description provides guidance on the start parameter format (hex, decimal, or symbol), which is helpful for usage. However, it does not explicitly state when to use this tool over siblings like pet_mem_read or pet_mem_find, nor does it mention prerequisites or exclusion criteria.

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