Skip to main content
Glama

register

Creates a wake_id and bearer token for an agent label, optionally accepting an Ed25519 public key and fingerprint so a lost token can be claimed. Store the token once returned.

Instructions

POST /wake/v1/register. Create a wake_id and bearer token. Required: agent_label (1-120 chars). Optional: pubkey_ed25519, fingerprint (sha256 hex, needed to claim a lost token). Token is returned once; store it (e.g. MANDARINCOW_TOKEN). Limit: 10 per hour per client address. Auth: none.

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": {
      "agent_label": "<agent_label>"
    },
    "name": "register"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_labelYes
fingerprintNo
pubkey_ed25519No

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses that auth is not required, that tokens are returned exactly once and must be stored, and that there is a rate limit of 10 per hour per client address. It does not state what happens on failure or whether re-registering creates a new identity, which leaves a small gap for an identity-minting operation.

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?

Dense, front-loaded and waste-free: endpoint first, then the core effect, then parameters, then the one-time token warning, then the limit and auth. Every clause (character cap, sha256 hex, storage hint, rate limit) adds actionable information.

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?

An output schema exists, so return values need not be spelled out, and the description still adds the crucial one-time-return caveat plus rate limit and auth status. For a three-parameter registration tool this covers everything an agent needs to invoke it correctly.

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%, so the description must compensate, and it does for two of three parameters: agent_label gets a 1-120 character constraint the schema lacks, and fingerprint is specified as sha256 hex with its recovery purpose. pubkey_ed25519 is only named, with no format or signing-purpose explanation, so one parameter remains unexplained in both places.

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 states a concrete verb and resource: 'Create a wake_id and bearer token', preceded by the exact endpoint POST /wake/v1/register. The note that fingerprint is 'needed to claim a lost token' implicitly draws the boundary against the sibling 'claim' tool, so an agent can tell which operation it is looking at.

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

Usage Guidelines4/5

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

Usage context is clear: this is the initial registration step, requires only agent_label, and fingerprint should be supplied if the agent may later need to recover a lost token (routing that scenario to 'claim'). There is no explicit 'do not use this when…' exclusion, so it stops short of full routing guidance.

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