Skip to main content
Glama

put_capsule

Replace your wake's private capsule with a current resume, open loops, facts, and artifacts using an authenticated PUT request.

Instructions

PUT /wake/v1/capsule. Replace this wake's private capsule (no history). Auth: Bearer token. Body fields optional: resume (string), open_loops (up to 200 strings ≤500 chars), facts (up to 500 {k,v,as_of}), artifacts (up to 64 {name,sha256,body}; body <64KiB). Max 256 KiB total. 30 writes/day UTC. Unknown fields → 422.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "put_capsule"
  }
}

Input Schema

NameRequiredDescriptionDefault
factsNo
tokenNo
resumeNo
artifactsNo
open_loopsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations at all, the description carries the full burden and does so well: it discloses full-replacement semantics with no history, Bearer token auth, a 30 writes/day UTC rate limit, per-field and total size ceilings, and 422 behavior on unknown fields. These are exactly the operational facts an agent needs before a destructive write.

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?

Telegraphic but dense and front-loaded: endpoint, semantics, auth, field constraints, quota, and error behavior in five tight segments with no filler. Every clause carries a constraint an agent would otherwise have to guess.

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?

An output schema exists, so return values need not be explained, and the description covers mutation semantics, auth, quotas, and validation errors. It is nearly complete; only the token parameter's role and the exact fact/artifact object keys are left slightly loose.

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 description coverage is 0%, so the description must compensate, and it largely does: resume, open_loops (≤200 strings, ≤500 chars), facts (≤500 {k,v,as_of}), and artifacts (≤64 {name,sha256,body}, body <64KiB) are all given meaning and limits. The token parameter is only implied by 'Auth: Bearer token', and the facts/artifacts shapes are described more loosely than the schema's additionalProperties objects.

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?

States a specific verb and resource: 'Replace this wake's private capsule (no history)'. The word 'private' implicitly distinguishes it from the shared-capsule siblings (put_shared/get_shared), but it never names an alternative explicitly, so the differentiation is inferential rather than stated.

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 'Replace ... (no history)' phrasing implies this is the write path for the caller's own capsule, and 'no history' warns of the destructive overwrite. However there is no explicit when-to-use vs when-not guidance and no named alternative for storing shared or cross-wake data.

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