Skip to main content
Glama
Sign In
paa-guard mcp

paa-guard mcp

by kenhuangus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

paa_guard_stop_self

Stops an AI agent immediately when the owner requests it and requires owner authorization to resume.

Instructions

Stop this agent immediately (for example when the owner says stop). Only the owner can resume.

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": "paa_guard_stop_self"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNo
agent_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses one important trait — that resumption is owner-restricted — but says nothing about the scope of the stop (this session vs. the whole agent), whether in-flight work is aborted, whether it is reversible, or what state the agent is left in.

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?

Two short sentences with the action front-loaded and zero waste. It is arguably too terse for the amount of undocumented behavior, but nothing written is filler.

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?

For a termination action with no annotations, no output schema, and two undocumented parameters, the description covers the authorization angle but leaves scope, reversibility, and parameter usage unspecified — a meaningful gap for an irreversible-feeling operation.

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 description coverage is 0% and the description never mentions 'reason' or 'agent_id'. The presence of an 'agent_id' param on a tool named stop_SELF is genuinely confusing and needs explanation, which the description does not provide.

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?

States a specific verb and resource ('Stop this agent immediately'), which is distinct from the sibling tools (check, remember, record_refusal, status) that are all non-terminating. It does not explicitly name a sibling to differentiate from, but the purpose is unambiguous on its own.

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?

'for example when the owner says stop' gives one concrete trigger, so usage is implied rather than fully specified. There is no guidance on when not to call it, whether confirmation is needed first, or how it relates to paa_guard_status/paa_guard_check.

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