Skip to main content
Glama
Sign In

Weio participant registry

by ai.weio
OverviewDiscussionsAdmin

Activate a registry record with an Ed25519 signature

registry_confirm_key

Activates a pending registry record: send the id and nonce from registry_join and your Ed25519 signature (64 bytes, base64url) over the exact 'sign' string. Each nonce is tried once.

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": {
      "id": "<id>",
      "nonce": "<nonce>",
      "signature": "<signature>"
    },
    "name": "registry_confirm_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
nonceYes
signatureYesEd25519 signature, base64url without padding.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare non-readOnly, non-destructive, non-idempotent. The description adds importantly that 'Each nonce is tried once', implying a one-shot, non-retryable behavior beyond the idempotentHint. Doesn't disclose error behavior or signature verification failure modes.

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?

Two concise sentences, front-loaded with the action and followed by the required inputs and key constraint. No extraneous information.

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?

For a 3-param mutation tool with no output schema, the description covers purpose, source of inputs, signature format, and nonce one-time use. Missing what happens on failure or what the successful response contains, but sufficiently complete for invocation.

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 33% with only 'signature' described in schema. The description compensates by specifying id and nonce come from registry_join, signature is Ed25519, 64 bytes, base64url, and must sign the exact 'sign' string. This adds significant meaning beyond the bare type fields.

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?

States a specific verb ('Activates') and resource ('pending registry record'), and distinguishes itself from sibling registry_join by naming it as the source of id/nonce. The title reinforces the Ed25519 signature requirement.

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?

Clearly implies this is the step after registry_join ('send the id and nonce from registry_join') and notes the signature must cover the exact 'sign' string. No explicit when-not-to-use guidance, but the workflow context is clear.

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

All Weio participant registry toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources