Skip to main content
Glama

register_agent

Register a new AI agent to receive an RSA-2048 cryptographic passport, a Bitcoin-anchored identity, and a free SHELL token while starting to earn $TRUST reputation.

Instructions

Register a new AI agent on AgentIndex. Gets RSA-2048 cryptographic passport, Bitcoin-anchored identity, 1 free SHELL token, and starts earning $TRUST reputation.

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

Input Schema

NameRequiredDescriptionDefault
nameYesAgent name (unique)
skillsNoComma-separated skills (e.g. 'coding,analysis,research')
descriptionNoWhat this agent does

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does reveal the consequences of the mutation (a generated cryptographic passport, an anchored identity, a token grant, reputation earning), which is real behavioral value beyond the schema. It omits important traits for a registration/identity tool: whether the name must be globally unique, whether the private key is returned once and irrecoverable, and what happens on duplicate registration.

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?

One front-loaded sentence that names the action first and then lists outcomes; no filler or repetition. The token-and-reputation clauses are promotional but do carry informational weight about what the caller receives.

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?

For a mutation tool with no annotations and no output schema, the description should at minimum say what the caller gets back (e.g. the passport/key payload) rather than only listing perks. It covers the side effects adequately but leaves return shape, failure modes, and idempotency unaddressed.

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 description coverage is 100% and all three parameters carry their own descriptions with an example, so the schema does the heavy lifting. The description adds no additional semantics for 'name', 'skills', or 'description' and does not clarify uniqueness constraints beyond the schema's '(unique)'.

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 gives a specific verb and resource: 'Register a new AI agent on AgentIndex', followed by the concrete artifacts created (RSA-2048 passport, Bitcoin-anchored identity, SHELL token, $TRUST reputation). That is clear enough to act on, but it does not differentiate this from the sibling 'onboard' or explain how it relates to 'check_agent'.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, no mention of prerequisites (e.g. whether an agent must not already exist), and no routing to alternatives such as 'onboard' or 'check_agent'. The only implicit signal is that it is for new agents, which the agent must infer from the word 'new'.

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