Skip to main content
Glama
Sign In
capy-fleet

capy-fleet

by Takumixbt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Stop a running Capy thread

capy_stop
DestructiveIdempotent

Stop a running Capy agent thread to cancel work that is going wrong or burning credits. Work already committed is not undone.

Instructions

Stop a Capy agent thread that is currently running. Use this to cancel work that is going the wrong way, or to stop a thread that is burning credits on the wrong problem. Work already committed by the agent is not undone.

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": {
      "thread_id": "<thread_id>"
    },
    "name": "capy_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
thread_idYesThread id to stop, e.g. "jam_123".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate destructiveness and idempotency. Description adds that committed work remains, clarifying the scope of stopping. No contradictions or additional details on permissions or side effects.

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 concise sentences, each adding value: the first states the action, the second provides usage context and a behavioral caveat.

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?

For a simple 1-param tool with good annotations, the description covers purpose, when to use, and key limitation. Could mention post-stop state or error handling, but sufficiently complete.

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 coverage is 100% for the single parameter, so baseline 3 applies. The description does not add meaning beyond the schema's own description of thread_id.

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 uses a specific verb 'Stop' and resource 'Capy agent thread', distinguishing it from sibling tools like capy_list or capy_status.

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?

Provides clear guidance on when to use ('cancel work going wrong', 'stop burning credits') and what it does not do ('work committed not undone'), but does not mention alternatives like checking status first.

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