Skip to main content
Glama
bruhsb

paperclip-mcp

by bruhsb
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

paperclip_update_agent

DestructiveIdempotent

Update an agent's name, title, capabilities, status, heartbeat, runtime, or adapter configuration to modify its identity and operational behavior.

Instructions

Update an agent's name, title, capabilities, status, heartbeat, runtime, or adapter config.

Args:

  • agentId: string — Agent UUID (example: "agt_abc123")

  • name: string (optional) — New display name

  • title: string (optional) — New job title

  • capabilities: string (optional) — Updated capability description

  • status: string (optional) — New status (e.g. active, paused)

  • runtimeConfig.heartbeat.enabled: boolean (optional) — Enable/disable scheduled heartbeats

  • runtimeConfig.heartbeat.intervalSec: integer (optional) — Heartbeat interval in seconds

  • runtimeConfig.heartbeat.cooldownSec: integer (optional) — Min seconds between runs

  • runtimeConfig.heartbeat.maxConcurrentRuns: integer (optional) — Max concurrent runs

  • adapterConfig.model: string (optional) — LLM model identifier

  • adapterConfig.maxTurnsPerRun: integer (optional) — Max LLM turns per run

  • adapterConfig.timeoutSec: integer (optional) — Hard timeout in seconds

  • adapterConfig.instructionsFilePath: string (optional) — Path to AGENTS.md

Returns: Returns the updated agent object with all fields.

Examples:

  • Use when: adjusting an agent's heartbeat interval or updating its capabilities description

  • Don't use when: you need to update permissions — use paperclip_update_agent_permissions (board-only) instead

Error Handling:

  • 400: validation failure → check field types and enum values

  • 401: authentication failed → check PAPERCLIP_API_KEY

  • 404: agent not found → verify ID with paperclip_list_agents

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentIdYesAgent UUID
nameNoNew display name
titleNoNew job title
capabilitiesNoUpdated capability description
statusNoNew status (e.g. active, paused)
runtimeConfigNoAgent runtime configuration
adapterConfigNoAdapter configuration for the agent process

Tool Definition Quality

A4.1/5.0
Behavior3/5

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

Annotations already provide destructiveHint: true and idempotentHint: true. The description adds error handling details (400, 401, 404) and notes that the updated agent object is returned. It does not contradict annotations but also does not significantly expand on behavioral traits beyond what the annotations imply.

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

Conciseness4/5

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

The description is well-structured into sections: purpose, Args, Returns, Examples, Error Handling. It is front-loaded with the main purpose. Although it is a bit long, every section earns its place and the format is easy to scan.

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 complexity (7 parameters, nested objects) and no output schema, the description covers purpose, all parameters with examples, return type, error handling, and usage guidance. It does not detail the fields of the returned object, but otherwise is thorough.

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%, so each parameter already has a description. The description reinforces these with a structured Args list that includes examples (e.g., 'example: agt_abc123' for agentId). This adds minor extra value but is not essential.

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 starts with a clear verb+resource: 'Update an agent's name, title, capabilities, status, heartbeat, runtime, or adapter config.' It lists the specific updatable fields and includes an examples section that distinguishes it from the sibling tool paperclip_update_agent_permissions.

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

Usage Guidelines5/5

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

The description explicitly states when to use (e.g., adjusting heartbeat interval or capabilities) and when not to use (updating permissions, with a direct reference to paperclip_update_agent_permissions). This provides clear guidance on alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bruhsb/paperclip-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server