Skip to main content
Glama

register_agent

Register an AI agent by generating a cryptographic identity (DID and keypair) for secure on-network operations. 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?

With no annotations, the description fully discloses side effects (local key file with chmod 0600, network registration), irreversibility, and key regeneration impossibility. This goes well beyond basic purpose.

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?

Description is well-structured, front-loading purpose, then details, usage, and side effects. Every sentence adds value without redundancy.

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?

Given complexity (identity creation, network registration), the description covers setup prerequisites, side effects, return format, and failure cases. Output schema complements but description is self-sufficient.

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 covers the single parameter with description and default. The description repeats the parameter details and environment variable fallback, adding marginal 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?

Description clearly states the tool registers a new AI agent on the Agent Veil Protocol network, detailing the cryptographic identity and DID creation. It distinguishes from sibling tools by positioning it as a one-time setup before write operations.

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?

Explicitly advises calling once before write operations and suggests using get_my_agent_info to verify setup. While it doesn't list when not to use, the context of first-time setup and permanence is clear.

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