Skip to main content
Glama
Sign In
swarmix-mcp

swarmix-mcp

by diegotorreslopez81
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

pause_agent

Stop an active agent from running scheduled actions by providing its ID. This tool halts automated outreach tasks in the swarmix-mcp server.

Instructions

Pause an active agent. It will stop running scheduled actions.

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": {
      "agentId": "<agentId>"
    },
    "name": "pause_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentIdYesThe agent ID to pause

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden. It explains that pausing stops scheduled actions, which is helpful behavioral context. However, it omits reversibility (can it be resumed?), effects on currently executing actions, or idempotency concerns for this state-changing 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?

Two efficiently structured sentences. The first states the action, the second explains the consequence. No filler or redundancy; every word earns its place.

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 single-parameter state change tool with 100% schema coverage and no output schema, the description adequately covers the essentials. It could improve by mentioning reversibility via resume_agent, but the current level is acceptable for this complexity tier.

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%, establishing a baseline of 3. The description adds the constraint that the agent should be 'active,' which provides semantic context beyond the schema's literal 'agent ID to pause.' However, it does not elaborate on the parameter format or validation rules.

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 clearly identifies the verb (Pause), resource (agent), and scope (active), along with the specific effect (stop running scheduled actions). It implicitly distinguishes from siblings like resume_agent and create_agent, though it doesn't explicitly reference them.

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 provides implied usage guidance by explaining the effect (stops scheduled actions), suggesting when to use it. However, it lacks explicit when/when-not guidance or named alternatives like resume_agent for the reverse operation.

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