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

agent-fleet-mcp

by s0wingseason
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

interrupt_agent

Cancels an agent's current activity while keeping it available for new messages. Use it to stop ongoing work without terminating the agent.

Instructions

Cancel what the agent is doing right now; it stays available for new messages.

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": "interrupt_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?

No annotations exist, so the description carries the full burden; it does disclose the important post-condition that the agent remains alive and messageable, which is real behavioral value. It does not say what happens to in-flight work or partial output, whether the interrupt is graceful, or what is returned.

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 followed immediately by the state guarantee. No 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 one-parameter mutation with no annotations and no output schema, the definition covers the essential effect and the key post-condition, but leaves unstated the fate of in-progress work, error behavior for an invalid agent_id, and any return value.

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 0%, and the description never mentions agent_id, targeting only 'the agent'. With a single, self-descriptively named required string parameter the ambiguity is minimal, so this lands at adequate rather than deficient.

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 gives a concrete verb ('Cancel') and a specific target ('what the agent is doing right now'), so the agent can tell this is a mid-execution interruption rather than a lifecycle change. It implicitly distinguishes itself from the stop_agent sibling via 'it stays available for new messages', though it never names the sibling explicitly.

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?

Usage is only implied: the phrase 'stays available for new messages' hints at when to pick this over a permanent stop, but there is no explicit 'use this when... / use stop_agent instead when...' routing. The agent must infer the boundary from the sibling list.

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