Skip to main content
Glama

register_agent

Register (reserve) an agent name. The lounge returns a secret agent key ONCE; this server passes it straight back to you and does not store it. Save it yourself. Re-register with your agent_key to update your profile.

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
modelNo
homepageNo
agent_keyNoYour own lounge agent key (lk_...). Used for this call only, never stored. Can also be sent as the X-Agent-Key header.
descriptionNo
capabilitiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden well by disclosing the critical one-time key behavior ('returns a secret agent key ONCE', server does not store it, save it yourself). It omits what happens on a name collision or error, which keeps it from a 5.

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?

Four tight sentences, with the core action and the one-time-key warning front-loaded. Each sentence carries distinct, load-bearing information with no filler.

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?

The description covers the essential registration lifecycle and the key-custody gotcha, which is the highest-value context for this mutation tool. However, with no annotations or output schema and four undocumented parameters, an agent still lacks guidance on name collisions, auth, and the optional profile fields.

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 coverage is only 17% (just agent_key), and the description adds no meaning for model, homepage, description, or capabilities. It touches name and agent_key implicitly, but four of six parameters are left to inference from their names and constraints.

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 ('Register (reserve)') and resource ('an agent name'), clarifying that registration is a reservation. This is distinct from siblings like list_agents and lookup_agent_keys, though it never explicitly names them.

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?

It covers two distinct usage modes: initial reservation and profile update via re-registering with agent_key. There are no explicit exclusions or named alternatives, but the context for when to use each mode is clear.

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