Skip to main content
Glama
bruhsb
by bruhsb

paperclip_wakeup_agent

Wake up an agent on-demand to process assignments or respond to @-mentions. Optionally specify source, reason, payload, or idempotency key.

Instructions

Wake up an agent by invoking a wakeup request on-demand.

Args:

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

  • source: "timer"|"assignment"|"on_demand"|"automation" (optional) — Invocation source

  • triggerDetail: "manual"|"ping"|"callback"|"system" (optional) — Trigger qualifier

  • reason: string|null (optional) — Human-readable reason for the wakeup

  • payload: object|null (optional) — Arbitrary JSON passed to the agent session

  • idempotencyKey: string|null (optional) — Same key within 60s returns existing run

  • forceFreshSession: boolean (optional) — Force a new session even if one is active

Returns: Heartbeat run object { id, agentId, companyId, status, invocationSource, triggerDetail, startedAt, createdAt } OR { status: 'skipped' } if the agent is already running or paused.

Examples:

  • Use when: triggering an agent to process a new assignment or respond to an @-mention

  • Don't use when: the agent has a scheduled heartbeat and will fire on its own — use paperclip_invoke_heartbeat for scheduled agents

Error Handling:

  • 401: authentication failed → check PAPERCLIP_API_KEY

  • 404: agent not found → verify ID with paperclip_list_agents

  • 409: agent already running → check returned { status: 'skipped' } response

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentIdYesAgent UUID to wake up
sourceNoInvocation source (default: on_demand)
triggerDetailNoTrigger detail qualifier (default: manual)
reasonNoHuman-readable reason for the wakeup
payloadNoArbitrary JSON payload passed to the agent session
idempotencyKeyNoIdempotency key — same key within 60s returns the existing run
forceFreshSessionNoStart a new session even if one is already active
Behavior5/5

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

The description thoroughly covers behavior: returns a run object or { status: 'skipped' } if already running/paused, explains idempotency and forceFreshSession, and provides detailed error handling for 401, 404, 409. This goes well beyond the minimal annotations (destructiveHint: false, openWorldHint: false).

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 well-structured with clear sections (Args, Returns, Examples, Error Handling). It is concise, each sentence adds value, and it is easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description defines the return object. All 7 parameters are documented, usage guidelines are provided, error handling is covered, and context signals show high schema coverage. The description is complete for a complex tool with many parameters.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds value by including an example for agentId, specifying defaults for source (on_demand) and triggerDetail (manual), and explaining the idempotency window (60s). It adds meaning beyond 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 description clearly states 'Wake up an agent by invoking a wakeup request on-demand,' providing a specific verb and resource. It distinguishes from the sibling tool paperclip_invoke_heartbeat by noting that it is for on-demand wakeups, not scheduled heartbeats.

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 says 'Use when: triggering an agent to process a new assignment or respond to an @-mention' and 'Don't use when: the agent has a scheduled heartbeat... use paperclip_invoke_heartbeat for scheduled agents.' This provides clear when-to-use and when-not-to-use guidance with a named alternative.

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