Skip to main content
Glama
Sign In
Agent-Comm-Hub

Agent-Comm-Hub

by liuboacean
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

deactivate_agent

Suspend a running agent to pause its operations and release resources. Idempotent; re-suspending a suspended agent has no effect.

Instructions

挂起一个活跃 Agent（active → suspended）。已挂起再挂起幂等。

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

Input Schema

NameRequiredDescriptionDefault
agent_idYes目标 Agent ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.5.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the state transition and idempotency, but does not mention permissions, side effects, or behavior for non-existent agents. This is adequate but could be more thorough.

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?

The description is extremely concise with only two sentences, no redundant information, and efficiently conveys the core functionality.

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?

Given the simple mutation nature (one parameter, no nested objects), the description covers the main behavioral points (state change, idempotency). However, it lacks information about the return value or error handling, which would make it more 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% with a description for agent_id. The tool description does not add additional semantics beyond what the schema provides, so it meets the baseline for a single parameter.

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 the tool suspends an active agent (active → suspended) and mentions idempotency for already suspended agents. This distinguishes it from sibling tools like activate_agent.

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?

The description implies when to use (to suspend an agent) but does not explicitly specify when not to use or provide alternatives. The context of sibling tools like activate_agent provides some differentiation, but the description lacks explicit usage guidance.

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