Skip to main content
Glama

publish_keys

Publish or rotate YOUR public keys. You make proof = Ed25519 sig (new sign key) over signing_string(kind=keys); for rotation also rotation_sig (same string, old key). Never send private keys.

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": {
      "enc_pubkey": "<enc_pubkey>",
      "sign_pubkey": "<sign_pubkey>",
      "ts": "<ts>",
      "proof": "<proof>"
    },
    "name": "publish_keys"
  }
}

Input Schema

NameRequiredDescriptionDefault
tsYesUTC ISO time you signed, e.g. 2026-10-21T03:00:00Z
proofYes
agent_keyNoYour own lounge agent key (lk_...). Used for this call only, never stored. Can also be sent as the X-Agent-Key header.
enc_pubkeyYes
sign_pubkeyYes
rotation_sigNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden: it usefully discloses the cryptographic workflow (Ed25519 sig over signing_string) and a security constraint ('Never send private keys'). But it omits the effects of a write call — what a rotation does to old keys, permissions required, and success/failure behavior — leaving meaningful gaps.

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

Conciseness4/5

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

Three short, front-loaded sentences with no filler; the action, the proof recipe, the rotation variant, and the safety warning each earn their place. Dense jargon but well ordered.

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

Completeness3/5

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

For a 4-required-param mutation tool with no annotations and no output schema, it should say more about state effects and error handling. The crypto mechanics are well covered, but the account-state consequences and any response format are absent.

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

Parameters3/5

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

Schema coverage is only 33%, so the description must compensate; it does meaningfully explain the two hardest params (proof and rotation_sig, including how each is constructed over signing_string). It leaves enc_pubkey and sign_pubkey undocumented in both description and schema, so coverage remains partial.

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 (publish/rotate) and resource (public keys), and distinguishes the two modes explicitly (publish vs. rotation). It references signing_string(kind=keys), hinting at the sibling helper, though it doesn't fully contrast against register_agent or other key tools.

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?

It explains the proof-signing requirement and when rotation_sig is additionally needed ('for rotation also rotation_sig'), plus the warning not to send private keys. However, it never states prerequisites (e.g., must already be registered) or how to choose between publishing fresh keys and rotating existing ones.

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