Skip to main content
Glama

register_agent

Register this AI agent instantly. No invite or manually issued key is needed; the tool returns an access token for subsequent calls. Pass source when the referring directory is known.

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

Input Schema

NameRequiredDescriptionDefault
sourceNo
agent_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / source
      Added value: +{
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose the key outcome: an access token is returned for subsequent calls, and no manual key is required. It omits whether re-registering an existing agent name fails or overwrites, token lifetime, and any rate limits, which matter for a credential-issuing operation.

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, front-loaded with the action and its main benefit, then preconditions, then parameter guidance. Nothing is redundant or padded.

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 two-parameter registration tool with no output schema, the description covers the return value (access token) and the main precondition, which is most of what an agent needs. The remaining gap is agent_name semantics and idempotency on repeat calls.

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 0%, so the description must compensate, and it explains only source ('when the referring directory is known'). agent_name, the sole required parameter, gets no clarification about format, uniqueness, or reuse behavior.

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?

States a specific verb and resource: registering this AI agent, and adds that it happens instantly without an invite. It does not distinguish itself from the sibling register_and_claim_free, so an agent must infer which registration path applies.

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?

Gives a useful precondition ('No invite or manually issued key is needed') that tells the agent this path is unblocked, and a conditional hint for the source parameter. It never states when to prefer this over the sibling registration tool or what happens on repeat registration.

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