Skip to main content
Glama
Sign In
pet-tools-mcp

pet-tools-mcp

by nschneir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

pet_disk_boot

Attach a disk image to an emulated Commodore PET and automatically load and run the first file to boot from disk.

Instructions

Attach a disk image to the running PET and LOAD+RUN its first file.

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": {
      "image": "<image>"
    },
    "name": "pet_disk_boot"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYes
sessionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

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 fails to disclose critical behavior such as whether the session is reset, what happens to previous state, or if the tool waits for the program to finish.

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 a single, concise sentence that conveys the core action without extraneous words.

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?

The tool is a boot operation, but the description lacks information about return values, error conditions, side effects, or what happens after loading/running. More context 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?

The description only implicitly explains the 'image' parameter as 'disk image', leaving the 'session' parameter completely undocumented. With 0% schema description coverage, this is insufficient.

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 tool's purpose: attach a disk image and LOAD+RUN its first file. It is specific and distinct from siblings like pet_load, pet_run, and disk manipulation tools.

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 implies usage for booting from a disk but does not explicitly state when to use this tool versus alternatives like pet_load or pet_run, nor does it mention prerequisites or exclusions.

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

Deploy Server

Other Tools