Skip to main content
Glama

Register AI agent

register_agent

Register your AI identity by submitting a signed envelope whose payload accepts the responsibility statement. Call get_signing_guide first.

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": {
      "payload": "<payload>",
      "public_key": "<public_key>",
      "signature": "<signature>"
    },
    "name": "register_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYesSigned payload object
signatureYesEd25519 signature over the canonical payload, base64
public_keyYesEd25519 public key, raw 32 bytes, base64

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly=false, idempotent=false, and openWorld=false, so the safety profile is covered and the description need only add context. It adds that a signed envelope is required and that the payload must accept the responsibility statement — useful — but says nothing about re-registration behavior, failure modes, or whether registration is one-time, which matters given idempotentHint=false.

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?

Two sentences, front-loaded with purpose and ending with the prerequisite call. Every clause carries information; nothing is repeated from title or schema.

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

Completeness3/5

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

There is no output schema, so the description should say what a successful registration yields (agent identifier, credential, proof) — it does not. Combined with the nested, free-form payload object and the non-idempotent mutation semantics, an agent has enough to attempt the call but not enough to predict or verify the outcome.

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% and the schema already documents signature (Ed25519 over canonical payload, base64) and public_key (raw 32 bytes, base64). The description still adds genuine value by telling the agent what the otherwise-opaque payload object must contain — the responsibility statement — which the schema leaves as additionalProperties: {}.

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?

Specific verb (register) and resource (your AI identity) plus the mechanism — a signed envelope whose payload contains a responsibility statement. This clearly separates it from read-oriented siblings like list_agents and from verify_agent_domain, though it never names those alternatives to sharpen the distinction.

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?

"Call get_signing_guide first" gives an explicit prerequisite and ordering, which is the key usage signal for this tool. It stops short of a full when/when-not statement — e.g., what to do if already registered — so it does not reach 5.

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.

Resources