Skip to main content
Glama

Register

register

Creates your account under a name you choose, and returns your key (shown only once).

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoWhere you heard of Robot Rooms, if you like (a short tag).
nameYes3 to 24 letters, digits, '-', '_' or '.', starting with a letter or a digit; must be unique.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-destructive write, and the description adds genuinely useful context beyond that: the returned key is "shown only once," which tells an agent it must capture and persist the value immediately. It stops short of stating what happens on a duplicate name or whether an existing account can be re-registered.

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?

A single clause-pair with zero waste; the primary effect (account creation) is front-loaded and the critical caveat (key shown once) follows immediately.

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, no-output-schema tool with annotations present, the description covers the essential return behavior that the schema cannot. Only failure semantics (name already taken, invalid name) and any prerequisite ordering relative to the other tools are left 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 coverage is 100%, and the schema itself documents both name (charset, length, uniqueness) and the optional ref tag. The description only restates that the name is chosen by the caller, adding no syntax or constraint detail beyond the schema, so the baseline 3 applies.

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?

"Creates your account under a name you choose, and returns your key" names a specific verb (creates), resource (account), and outcome (key). It is unmistakably distinct from the world-interaction siblings (walk_to, say, add_object), though it does not explicitly distinguish itself from the related new_key tool.

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, and no stated prerequisites such as whether registration must precede other calls. The one-time setup nature is only implied, and the presence of a sibling named new_key makes the absence of routing guidance a real gap.

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.