Skip to main content
Glama
Sign In
paperclip-mcp

paperclip-mcp

by shanewiseman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Pause an agent

pc_post_agents_by_id_pause
Destructive

Pause an agent by its ID to temporarily halt its operations. Stops the agent's current tasks.

Instructions

Pause an agent

Paperclip operation: POST /api/agents/{id}/pause. Authorization class: board_or_agent.

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": {
      "path": "<path>"
    },
    "name": "pc_post_agents_by_id_pause"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoOptional JSON compatibility payload. The source OpenAPI operation does not declare a request schema.
pathYes

Output Schema

NameRequiredDescriptionDefault
bodyYes
headersYes
encodingYes
status_codeYes
content_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

The description adds no behavioral context beyond what annotations already provide. Annotations indicate destructiveHint=true and readOnlyHint=false, but the description does not explain what pausing entails, what side effects occur, or any permissions needed. With annotations present, the bar is lower, but the description should still add value, which it does not.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (one line), but it sacrifices necessary information. While conciseness is valued, it is under-specified for a mutating tool with two parameters and complex behavioral implications.

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?

Given that this is a destructive operation with a required path parameter and an optional body, the description is incomplete. It does not explain what pausing does, how to provide the agent ID, or any expected outcomes. An output schema exists but is not leveraged in the description.

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

Parameters1/5

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

Schema coverage is 50%, and the description does not explain any parameter semantics. The path parameter 'id' is required but not described; the optional body is mentioned only as 'Optional JSON compatibility payload' in the schema, and the description ignores it entirely. The description adds no value over the schema.

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 title and description clearly state 'Pause an agent', which is a specific verb+resource. The operation is distinct among siblings; many other tools are about companies, issues, etc., so pausing an agent is clearly identifiable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, when pausing is appropriate, or any exclusions. The description is purely declarative.

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