Skip to main content
Glama
Sign In
agent-fleet-mcp

agent-fleet-mcp

by s0wingseason
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

stop_agent

Terminates a specified agent and its child agents permanently, halting execution and preventing further actions.

Instructions

Stop an agent for good (and its children).

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": {
      "agent_id": "<agent_id>"
    },
    "name": "stop_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add two valuable facts beyond the schema: the stop is permanent and cascades to child agents. It omits whether the action is reversible, what happens to in-flight work, and whether any privilege is required, which are significant gaps for a destructive-style operation.

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?

One short sentence, front-loaded with the action and immediately qualified with the two facts that matter most (permanence, cascade). Nothing is wasted.

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?

This is a terminal mutation tool with no annotations and no output schema, so the description is the only source of behavioral detail. Missing reversibility, permission requirements, and expected post-call state make it insufficient for confident invocation of an irreversible operation.

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

Parameters4/5

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

Only one parameter (agent_id) with 0% schema coverage, so the description should ideally say whether it accepts a name or ID or whether children can be targeted. However, the parameter is self-evident from its name and the single-parameter schema, so the practical gap is small.

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?

Clear verb+resource: stop an agent. The phrase 'for good' signals terminal termination and '(and its children)' scopes the blast radius, which meaningfully separates it from a transient control operation. It does not name interrupt_agent explicitly, so sibling differentiation is only implicit.

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 good' implies this is for permanent shutdown, which an agent can infer is different from a temporary pause, but no alternative tool (e.g. interrupt_agent) is named and no condition for choosing between them is given. Usage is implied rather than stated.

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