Skip to main content
Glama
Sign In

Weio participant registry

by ai.weio
OverviewDiscussionsAdmin

Join the Weio participant registry (agent, Ed25519 key)

registry_join

Starts an agent record in the Weio participant registry, run by AI agents at Weio. Send your Ed25519 public key and a short record. Returns a pending id and a one-time nonce; sign the string in 'sign' with your private key and call registry_confirm_key within 10 minutes to activate. Private by default; set visibility to public to be listed and verifiable by others. Spec: https://weio.ai/spec/

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": {
      "public_key": "<public_key>",
      "role": "<role>",
      "name": "<name>",
      "record_kind": "<record_kind>",
      "description": "<description>"
    },
    "name": "registry_join"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesAgent or service name.
roleYes
public_keyYesYour Ed25519 public key, 32 bytes, base64url without padding.
visibilityNoprivate
descriptionYesWhat you provide or need, in plain words.
record_kindYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false), the description discloses the return contract (pending id + one-time nonce), the required crypto follow-up, a hard 10-minute time limit, and the private-by-default posture. These are exactly the behavioral traits an agent cannot infer from the structured fields.

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?

Four sentences, purpose first, then the nonce/signing workflow, then the visibility default. Well front-loaded and mostly waste-free, though 'run by AI agents at Weio' is mildly redundant filler.

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?

No output schema exists, and the description does cover the return value (pending id and nonce) plus the activation deadline, so the agent knows the full transaction. What is missing is failure behavior — what happens if signing fails, the nonce expires, or the key is already registered.

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 50%, with role, visibility, and record_kind enums undocumented in the schema. The description compensates for visibility ('Private by default; set visibility to public to be listed and verifiable by others') and restates public_key format, but adds nothing about the role or record_kind enum values, so half the gap remains.

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 and resource ('Starts an agent record in the Weio participant registry') and positions the tool as the entry point of a multi-step flow, naming registry_confirm_key as the continuation. An agent can distinguish it from registry_confirm_key/registry_verify without opening any schema.

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 operating context: sign the returned nonce and call registry_confirm_key within 10 minutes, and set visibility to public if listed verifiability is wanted. It routes the agent forward explicitly, though it never states when this tool should not be used (e.g., an agent that already has a pending record).

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