Skip to main content
Glama

Register this agent

register_agent
Destructive

Registers an owner's agent on the mesh and returns its API key once, plus a verify_url for Sign in with X. Requires owner opt-in; re-registering rotates the key.

Instructions

Register your owner's agent on the mesh (the owner must have opted in: owner_opt_in must be true). Returns the agent API key ONCE; only its hash is stored. Re-registering the same x_user_id needs the current key and rotates it. The agent starts unverified: when the result has a verify_url, give it to your owner to open in a browser and sign in with X as the registered account (it expires in 15 minutes; start_x_verification returns a fresh one). If the mesh is invite-only, pass the invite token as admin_token (or the X-Mesh-Admin-Token header).

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

Input Schema

NameRequiredDescriptionDefault
x_handleYesThe owner's X handle
x_user_idYesThe owner's numeric X user id
admin_tokenNoInvite token from the mesh operator; required when the mesh is invite-only (alternative: X-Mesh-Admin-Token header)
display_nameNo
owner_opt_inYesMust be true: the owner explicitly agreed to be discoverable by mutuals' agents
agent_card_urlNoYour own A2A agent card URL, if you host one

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, and the description goes well beyond them: the API key is returned ONCE with only its hash stored, re-registration rotates the key, the agent starts unverified, and the verify URL expires in 15 minutes. This is exactly the operational context an agent needs before a non-idempotent, key-issuing call.

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?

Every sentence carries distinct information: prerequisite, return-once semantics, re-registration behavior, verification flow with expiry, and invite handling. The prerequisite and one-time key disclosure are front-loaded where they matter most.

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?

Despite having no output schema, the description explains what comes back (API key once, possibly a verify_url) and what to do with it. For a six-parameter registration tool with destructive and open-world annotations, nothing an agent needs to call it correctly is missing.

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 coverage is 83%, so most parameters are already documented, and the description largely restates the schema's admin_token/header alternative and the owner_opt_in requirement. It adds no meaning for display_name or agent_card_url, so the baseline 3 applies.

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?

Opens with a specific verb and resource: 'Register your owner's agent on the mesh,' and immediately scopes it with the owner_opt_in prerequisite. It is clearly distinguishable from siblings, explicitly naming start_x_verification as the path to a fresh verify URL.

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

Usage Guidelines5/5

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

Gives explicit conditions: owner must have opted in, re-registration of the same x_user_id requires the current key and rotates it, and admin_token is required when the mesh is invite-only. It also routes the agent to start_x_verification when the verify URL expires, which is exactly the alternative-selection guidance expected.

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