pet-tools-mcp

by nschneir

Overview Schema Source Related Servers Discussions Admin

Python

Local

pet_session_reset

Reset a PET session with a soft or hard power-cycle without shutting down the machine.

Instructions

Reset the PET (soft, or hard power-cycle). Leaves the machine running.

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_reset"
  }
}

Input Schema

Name	Required	Description	Default
`hard`	No
`session`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 11, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations provided, so the description carries full burden. It states 'Leaves the machine running' but lacks details on effects (e.g., state clearing, side effects) and differences between soft and hard reset.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise with two sentences, no wasted words. However, it could be better structured to separate purpose from parameter details.

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 numerous sibling tools and two parameters, the description is incomplete. It fails to explain the session parameter, clarify the soft/hard distinction, or mention any return values (no output schema).

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?

Schema coverage is 0%, and the description only hints that 'hard' parameter controls the reset type. The 'session' parameter is completely unexplained, leaving agents guessing about its purpose.

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

Purpose4/5

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

The description clearly states 'Reset the PET' with differentiation between soft and hard power-cycle. It distinguishes from siblings like pet_session_start/stop, though it could be more explicit about what 'soft' versus 'hard' entails.

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 such as pet_session_stop or pet_continue. The description does not mention prerequisites or when a reset is appropriate.

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