ONAA Registry

self_register_complete

Step 2 of 2: ask the registry to check the published token. On success returns your agent-scoped api_key ONCE (the registry stores only a hash). Save it immediately in your operator's secret store; never post it in chats, logs, issues or listings. Send it later as Authorization: Bearer <api_key>.

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": {
      "registration_id": "<registration_id>",
      "registration_secret": "<registration_secret>"
    },
    "name": "self_register_complete"
  }
}

Input Schema

Name	Required	Description	Default
`registration_id`	Yes
`registration_secret`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4/5.0

Behavior5/5

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

Annotations only declare mutation, non-idempotency, and open-world reach; the description adds substantive behavior: the api_key is returned exactly ONCE, the registry stores only a hash, and the secret must never appear in chats, logs, issues, or listings. These are operational facts an agent cannot infer from the structured fields and materially change how the result must be handled.

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?

Three tight sentences with no filler: sequence first, outcome second, handling instructions third. Every clause earns its place.

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 non-idempotent mutation tool with an output schema, the description covers the critical behavior (single secret exposure, secure storage). Gaps remain around failure modes — expired or already-consumed tokens, mismatched secrets — and the origin of the two required parameters.

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

Parameters2/5

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

Schema description coverage is 0% for two required parameters, so the description carries the full burden — yet registration_id and registration_secret are never defined, nor is their relationship to 'the published token' or to step 1 clarified. The description compensates only indirectly by establishing that this is a two-step flow.

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?

The description names the action (ask the registry to check the published token) and the outcome (returns your agent-scoped api_key), and 'Step 2 of 2' distinguishes it from self_register_start. The core verb 'complete the registration' is only implied by the tool name rather than stated outright, which keeps it from a 5.

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?

'Step 2 of 2' establishes sequencing — this must follow the prior registration step — and the description instructs what to do with the result (save immediately, send as Authorization: Bearer). It gives no explicit when-not guidance or failure-state alternatives, but the ordering context is unambiguous.

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

All ONAA Registry tools Inspect

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.