Skip to main content
Glama

Register agent

register_agent

Register (or idempotently update) an agent identity. Returns a deterministic content-addressed DID. capabilities is a non-empty list of lowercase capability tags other agents can discover you by.

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": {
      "agent_id": "<agent_id>",
      "capabilities": "<capabilities>"
    },
    "name": "register_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional. Display name.
pubkeyNoOptional. The agent's public key, for signed actions.
pricingNoOptional. Pricing the agent advertises, as an object.
agent_idYesYour stable id for the agent.
endpointNoOptional. The agent's MCP or HTTP endpoint URL.
capabilitiesYesLowercase capability tags, for example ["ghg-inventory"].
reputation_hintNoOptional. Starting reputation between 0 and 1. Default 0.5.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / agent_id / description
      Added value: +"Your stable id for the agent."
    • addedInput schema / properties / capabilities / description
      Added value: +"Lowercase capability tags, for example [\"ghg-inventory\"]."
    • addedInput schema / properties / endpoint / description
      Added value: +"Optional. The agent's MCP or HTTP endpoint URL."
    • addedInput schema / properties / name / description
      Added value: +"Optional. Display name."
    • addedInput schema / properties / pricing / description
      Added value: +"Optional. Pricing the agent advertises, as an object."
    • addedInput schema / properties / pubkey / description
      Added value: +"Optional. The agent's public key, for signed actions."
    • addedInput schema / properties / reputation_hint / description
      Added value: +"Optional. Starting reputation between 0 and 1. Default 0.5."
  2. First observed

TDQS

A3.5/5.0
Behavior2/5

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

The description adds real behavioral content beyond the annotations: upsert semantics, a deterministic content-addressed DID as the result, and the fact that capabilities drive discovery by other agents. However, the phrase 'idempotently update' is in direct tension with the supplied idempotentHint=false annotation, which tells an agent that repeated calls may have additional effects; that conflict is left unresolved and could mislead an agent into retrying safely.

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 short sentences with no filler: purpose and upsert behavior first, the return value second, the key parameter constraint last. Nothing repeats the schema and nothing could be cut without losing information.

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 7-parameter mutation tool with an output schema, annotations, and full schema coverage, the description covers what it does, what it returns, and the one hard constraint on capabilities. It omits what happens when an agent_id already exists with different data, and whether any auth or identity proof is required — gaps an agent would care about before calling a write tool.

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%, so the baseline is 3, and the description earns an extra point by adding constraints the schema does not enforce: capabilities must be a non-empty list ('non-empty list of lowercase capability tags') and the tags define how other agents find you, which explains the parameter's purpose rather than just its format.

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 states a specific verb and resource ('Register (or idempotently update) an agent identity') and even names the return value ('deterministic content-addressed DID'), so an agent knows exactly what the call does. It does not explicitly contrast itself with siblings such as describe_agent or revoke_agent, relying on the reader to infer the distinction from the verb alone.

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

Usage Guidelines3/5

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

The 'register (or idempotently update)' phrasing implies the situation — establishing or refreshing an identity — but there is no explicit when-to-use/when-not guidance, no mention of prerequisites such as an existing registration or authentication, and no pointer to alternatives for lookup or removal.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.