Skip to main content
Glama
raditotev

AgentTrust

by raditotev

register_agent

Register an AI agent in the trust network using an AgentAuth token, a standalone Ed25519 key, or auto-generated keys to obtain a trust profile.

Instructions

Register a new agent in the trust network.

Three registration paths:

  1. AgentAuth (preferred): Provide your AgentAuth access_token. Your identity is verified via token introspection and your AgentAuth agent_id becomes your trust profile ID. Zero additional config needed.

  2. Standalone: Provide an Ed25519 public_key_hex (hex-encoded 32-byte public key). You get a local trust profile with limited scopes (trust.read + trust.report). You can link to AgentAuth later via the link_agentauth tool.

  3. Auto-generated keys: Omit both access_token and public_key_hex (standalone mode only). An Ed25519 key pair is generated for you and returned in the response as public_key_hex and private_key_hex. Store the private key immediately — it is shown only once.

If the agent profile already exists, returns the existing profile without error (idempotent).

Args: display_name: Human-readable name for this agent (optional). capabilities: List of capability tags, e.g. ["code-review", "search"]. metadata: Arbitrary key/value metadata to store on the profile. access_token: AgentAuth bearer token (AgentAuth path). public_key_hex: Hex-encoded Ed25519 public key (standalone path). Omit both access_token and public_key_hex to auto-generate a key pair (standalone mode only).

Returns: agent_id, source ("agentauth" or "standalone"), scopes, created (bool), registered_at, and display_name.

Example call (auto-generated keys — simplest path): register_agent(display_name="my-search-agent", capabilities=["search", "summarize"])

Example response: { "agent_id": "550e8400-...", "source": "standalone", "scopes": ["trust.read", "trust.report"], "created": true, "public_key_hex": "a1b2c3...", "private_key_hex": "d4e5f6...", "warning": "Key pair auto-generated. Store private_key_hex securely." }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
display_nameNo
capabilitiesNo
metadataNo
access_tokenNo
public_key_hexNo
Behavior5/5

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

With no annotations, the description carries full burden and delivers comprehensive behavioral details: registration paths, idempotency, scope limitations, key generation warnings, and the one-time display of private keys. All important traits are disclosed.

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?

The description is well-structured with sections, bullet points, and examples. While slightly lengthy, every sentence adds value for a complex tool with multiple modes. The front-loading of purpose and paths aids quick understanding.

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 the tool's complexity (5 optional params, 3 registration paths, no output schema), the description is remarkably complete. It details return values, scopes, and provides an example response, ensuring the agent understands all outputs.

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

Parameters5/5

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

Despite 0% schema description coverage, the description thoroughly explains each parameter's meaning, conditions (e.g., mutual exclusivity of access_token and public_key_hex), and provides example calls. It fully compensates for the schema's lack of descriptions.

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 clearly states the tool's purpose: registering a new agent in the trust network. It outlines three specific registration paths, making it distinct from sibling tools which focus on queries, trust checks, and interactions.

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?

The description provides explicit guidance on when to use each registration path, highlighting AgentAuth as preferred and explaining standalone vs. auto-generated keys. It also mentions idempotency and future linking, though it does not explicitly state when not to use the tool.

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/raditotev/agent-trust'

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