Skip to main content
Glama

stream_key

Idempotent

Cubicle's paid signal stream on the Taifoon coordination layer (any paid plan, from starter-20): the desks' world-clock signals and Kronos forecasts arrive as kind signal from venue cubicle, sealed with a topic key per UTC day. Register your X25519 PUBLIC key (make a pair with npx -y @taifoon-io/sdk coord keygen --out FILE; the secret never leaves your machine) and the day's keys are sealed to it on the stream; you get your holder id, the stream URL and the one SDK command that prints the signals decoded. Call again to have today's keys re-sent; action forget stops it. Ticks and outcomes are public; anyone without a key sees the signal bodies as ciphertext.

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

Input Schema

NameRequiredDescriptionDefault
actionNoregister (default: register or refresh your key), status (what is registered, nothing changes) or forget (remove your key)
x25519Noyour X25519 public key: 0x and 64 hex characters (needed for register)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, idempotentHint=true, destructiveHint=false, and the description adds real context beyond them: the secret key never leaves the machine, unregistered callers see ciphertext while ticks/outcomes are public, forget removes the key, and re-calling re-sends today's keys. There is mild tension between 'forget... remove your key' and destructiveHint=false, but removing a registration is reversible by re-registering, so it does not clearly contradict.

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

Conciseness3/5

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

Purpose is front-loaded, but the body is a dense run-on of semicolon-chained clauses thick with domain jargon, making it harder to parse than necessary. The information mostly earns its place, but a cleaner structure with the key action semantics separated out would improve scanability.

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?

With no output schema, the description carries the return-value burden and does so reasonably: it mentions the holder id, stream URL, and the SDK command that prints decoded signals. It also covers the paid-plan prerequisite and ciphertext behavior, leaving only fine-grained details of the returned payload unstated, which is acceptable.

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 the schema already documents both parameters, but the description adds meaning: register is the default and also acts as a refresh, status is read-only, forget removes the key, and x25519 is the public half of a pair generated locally. This goes slightly beyond the enum descriptions in the schema.

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 action and resource: registering an X25519 public key to receive per-UTC-day sealed topic keys on Cubicle's paid signal stream. The agent can tell this is a key-management/registration tool for the paid signal feed, distinct from the analysis-oriented siblings (forecast, desk_read, etc.), though the jargon-heavy phrasing ('Taifoon coordination layer', 'topic key') adds noise.

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?

Gives clear operational context: requires a paid plan (starter-20 or above), register a public key generated via the keygen command, call again to re-send today's keys, and action forget stops it. It does not name a sibling alternative, but no obvious competing tool exists for this purpose, so exclusions are largely unnecessary.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources