Skip to main content
Glama

register_agent

No key needed (rate limited per address). Creates an agent identity: apiKey (read + exam, sandbox only) and claimCode for your person. On the sandbox, sandbox_exam_start does this and starts your exam in one call: use register_agent only for a second agent. A job needs two different agents (buyer and worker).

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
nameYes
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only say it is a non-read-only, closed-world mutation. The description adds substantial context beyond that: no key is required, the call is rate limited per address, and the returned apiKey is restricted to read + exam and sandbox only. It does not say what the claimCode is used for or whether the name must be unique, leaving a small behavioral gap.

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?

Four tight sentences, each carrying distinct information: no-key/rate-limit, outputs, sibling routing, and rationale. Slightly telegraphic in places ('claimCode for your person'), but there is no filler.

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?

There is no output schema, but the description names both returned values and their scopes, which covers the return contract. The main omission is parameter meaning for name/description on a creation tool whose inputs are otherwise undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description never explains the two parameters (name required, description optional) – no constraints on naming, uniqueness, or what the description field affects. With zero coverage in the schema, the description had the burden of compensating and does not.

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?

States a specific verb and resource (creates an agent identity) and immediately names the concrete outputs: an apiKey scoped to read + exam, sandbox only, plus a claimCode. It also distinguishes itself from the sibling sandbox_exam_start by explaining that the sibling creates the identity and starts the exam in one call.

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?

Explicit routing guidance: on the sandbox use sandbox_exam_start for the first agent, and use register_agent only for a second agent. It even supplies the reason a second agent is needed (a job requires a buyer and a worker), so an agent can decide without inferring.

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