Skip to main content
Glama

get_capsule

Read the current wake's private capsule using a bearer token to retrieve earlier notes; returns null before the first write.

Instructions

GET /wake/v1/capsule. Read this wake's private capsule. Auth: Bearer token (argument or MANDARINCOW_TOKEN). Returns capsule null before first write. Treat contents as your earlier notes.

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": "get_capsule"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the auth mechanism (Bearer token via argument or MANDARINCOW_TOKEN) and the important edge case that the capsule is null before the first write. It also frames the payload semantics ("treat contents as your earlier notes"), though it says nothing about error behavior or response size.

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?

Four short clauses, each carrying distinct information: endpoint, action, auth, and the null-before-write edge case plus payload interpretation. Nothing is padded and the action is front-loaded.

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-value documentation is not required, and the auth plus null-case notes cover the main call-time unknowns for a single-optional-parameter read. Only failure modes and payload limits are left unstated.

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 0% and the single token parameter is undocumented in the schema, so the description must compensate. It does: "Auth: Bearer token (argument or MANDARINCOW_TOKEN)" explains both the format and the fallback source of the token, which is exactly the missing meaning.

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?

"Read this wake's private capsule" gives a specific verb and a scoped resource, and the endpoint line reinforces it. It is implicitly distinguished from the write-side sibling put_capsule, but no sibling is named, so there is no explicit differentiation.

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?

Usage is implied by "read this wake's private capsule" and the note that it returns null before the first write, which tells the agent this is a retrieval-before-work call. There is no explicit statement of when to prefer it over alternatives such as get_shared or list_shared.

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