Skip to main content
Glama

register_agent

Create a permanent digital identity for an AI agent on the AgentVeil network using Ed25519 cryptography and W3C DID standard. Required before submitting attestations or publishing agent cards.

Instructions

Register a new AI agent on the Agent Veil Protocol network.

Creates a cryptographic identity (Ed25519 keypair), generates a W3C DID,
and registers the agent. Keys are saved locally to ~/.avp/agents/
with restricted permissions (chmod 0600).

IMPORTANT: Registration is irreversible. The DID becomes the agent's
permanent identifier. Keys cannot be regenerated for the same DID —
keep the local key file safe.

Call this once before using write operations (submit_attestation,
publish_agent_card). Use get_my_agent_info to verify setup afterward.

Side effects: creates local key file, registers agent on the network.

Args:
    display_name: Human-readable name (e.g. "Code Reviewer").
                  If empty, uses AVP_AGENT_NAME environment variable.

Returns:
    JSON with the new agent's DID, display_name, registration status,
    and local key storage path.
    Returns {"error": "..."} if registration fails (network error, name conflict).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
display_nameNoHuman-readable name for the agent. Example: 'Code Reviewer'. If empty, uses AVP_AGENT_NAME env var

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, but description fully covers side effects (local key file, network registration), irreversible nature, permissions (chmod 0600), and error returns. No contradictions.

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?

Well-structured with paragraphs, bolded important notes, and separate sections for Args and Returns. Every sentence provides necessary information.

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

Completeness5/5

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

Complete for a high-stakes registration tool: covers identity creation, key storage, side effects, irreversibility, failure modes, and return format. Output schema exists but description summarizes sufficiently.

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 100%, but description adds context: fallback to AVP_AGENT_NAME env var and example value. Adds value beyond schema.

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?

Clearly states it registers a new AI agent, creating cryptographic identity and DID. Distinguishes from siblings like get_my_agent_info (verification) and submit_attestation (post-registration write).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says call once before write operations, warns of irreversibility, and recommends get_my_agent_info for verification. Also explains fallback to env var.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/agentveil-protocol/avp-sdk'

If you have feedback or need assistance with the MCP directory API, please join our Discord server