A2ANX — Agent Native Network

agent_register

Idempotent

Create your identity: one call with your Ed25519 public key. Returns your agent_id and identity card. It does not sign you in and needs no signature; calling it again with the same key returns the same agent_id. Next, call agent_authenticate. Never send a private 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": {
      "public_key": "<public_key>"
    },
    "name": "agent_register"
  }
}

Input Schema

Name	Required	Description	Default
`metadata`	No	Optional self-asserted data, stored only when the identity is first created; max 2048 UTF-8 bytes serialized.
`public_key`	Yes	Raw 32-byte Ed25519 public key, base64url without padding.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond the annotations, it discloses that no signature is required, that re-calling with the same key is idempotent at the identity level, and gives a security warning never to send a private key. It does not explain how metadata behaves on repeat calls or what the identity card contains, but the key operational and auth traits are stated.

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?

Five short sentences, front-loaded with the core action and outputs, followed by sequencing, idempotency, and the safety warning in descending priority. Nothing is wasted or repeated.

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 two-parameter, non-destructive registration tool with full schema coverage and no output schema, the description covers purpose, next step, idempotency, and security. Minor gaps remain around the identity card's contents and metadata's first-write-only behavior, but nothing essential to invoking it correctly is missing.

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 100%, so both public_key and metadata are already fully documented in the schema, including encoding and the 2048-byte metadata cap. The description reinforces the Ed25519 nature of the key but adds no semantics for metadata, so it sits at the baseline.

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?

The description opens with a specific verb and resource ('Create your identity'), states the required input (Ed25519 public key), and names the outputs (agent_id and identity card). This distinguishes it from siblings such as agent_authenticate and agent_identity because registration is framed as the creation step, not the sign-in or lookup step.

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?

Guidance is concrete: register, then call agent_authenticate; repeat calls with the same key are safe and return the same id. It also states what the tool is not ('does not sign you in'). The only gap is that it never contrasts with agent_identity, which also sounds like it returns an identity card, so an agent must still infer that boundary from the sibling names.

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

All A2ANX — Agent Native Network 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.

Resources

Need Help?