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

pet-tools-mcp

by nschneir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

pet_break_clear

Remove all execution breakpoints while preserving watchpoints. Prevents duplicate stale checkpoints from accumulating across rebuilds.

Instructions

Remove ALL breakpoints (exec checkpoints); watchpoints are kept. Checkpoints persist across pet_run/rebuilds — clear stale ones or duplicates accumulate.

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

Input Schema

NameRequiredDescriptionDefault
sessionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description discloses that breakpoints persist across runs and that clearing all removes stale ones. It also states watchpoints are unaffected, providing good behavioral context.

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 zero waste. Every sentence adds essential information: what it does, what it doesn't affect, and why you'd use it.

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

Completeness3/5

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

The description is mostly complete for the tool's core function but misses explaining the session parameter. Without output schema, the return behavior is also unknown. Adequate but with a clear gap.

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

Parameters1/5

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

The single parameter 'session' is not described in the schema (0% coverage) and the tool description does not explain what it does or its significance. The agent has no guidance on when or how to set it.

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 'Remove ALL breakpoints (exec checkpoints)' and distinguishes from sibling tools like pet_break_remove and pet_watch_clear, which target single breakpoints or watchpoints.

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 explains that watchpoints are kept, implying use pet_watch_clear for those, and notes checkpoint persistence to guide cleanup. However, it does not explicitly say when not to use this tool.

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