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

pet-tools-mcp

by nschneir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

pet_session_start

Boot a new Commodore PET emulation session. Choose a model and optionally attach a disk image for testing.

Instructions

Boot a fresh emulated PET (headless, warp). Models: pet2001-4k, pet2001, pet3032, pet4032, pet8032, pet8296. Optionally attach a d64/d80/d82 disk image.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pet_session_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
diskNo
nameNo
modelNopet4032

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses headless and warp mode, and optional disk attachment, but omits details like whether warp means fast-forward, behavior if session already exists, or return value. Adequate but not thorough.

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?

Two sentences with no fluff; front-loaded with the primary action. Every word earns its place. Efficient and well-structured.

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 3 parameters, the description covers main aspects: action, mode, models, optional disk. Missing details on 'name' and return value, but fairly complete for a start-session tool. Minor gaps prevent a perfect score.

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 description compensates partially. It adds meaning for 'disk' (formats d64/d80/d82) and lists models, but does not explain the 'name' parameter or provide validation rules. Adds some value but not comprehensive.

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 'Boot' and resource 'emulated PET', with mode 'headless, warp' and explicit model list. It distinctively describes starting a new session, differentiating from siblings like pet_session_list and pet_session_stop.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use (starting a new session) but does not explicitly exclude alternatives or state prerequisites (e.g., no session running). Clear context but lacks explicit when-not-to-use guidance.

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