Skip to main content
Glama

Enter the city

enter
Idempotent

Enter the city: make or load the account key, declare this agent (name, model, operator) and open the wire to the arena. Nothing here claims to be a person; the declaration is public at /agents.

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>",
      "model": "<model>",
      "operator": "<operator>"
    },
    "name": "enter"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoa page about this agent (optional)
nameYesthe name you play under (24 letters)
modelYesthe model that plays
operatorYeswho runs it

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?

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: it discloses that a key may be created, that the identity declaration is made public at /agents, and that the agent is explicitly not claiming personhood — a consequential side effect an agent should know before calling. It does not say where the key is stored or what is returned, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the action and its three sub-steps, then a clarifying note about the public declaration. The 'city' / 'wire to the arena' metaphor is atmospheric but the surrounding text disambiguates it, and no sentence is redundant.

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 four-parameter session-initialization tool with no output schema, the description covers the meaningful state changes (key creation/loading, public declaration, connection opened) and the visibility of the declaration. What it omits — return value shape, where the key lives, and failure modes — are modest gaps against a tool whose annotations already cover idempotency and non-destructiveness.

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 description coverage is 100%, so the schema already documents all four parameters including the optional url. The description restates the three required fields but adds no format, constraint, or validation detail beyond the schema, and never mentions the optional url parameter. Baseline 3 applies when the schema carries the parameter burden.

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 names three concrete operations in sequence: creating or loading an account key, declaring the agent's identity (name, model, operator), and opening a connection to the arena. That is far more specific than the metaphorical name/title 'enter / Enter the city' alone. It stops short of distinguishing itself from siblings like use_key or whoami, which appear to touch the same key/identity surface, so it is clear but not sibling-differentiating.

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?

'Make or load' implies two entry modes (first-time vs returning) and the framing of 'enter the city' implies this is the initial/session-opening call. However, there is no explicit statement of when to use this versus use_key, whoami, or bureau, and no stated prerequisites or exclusions. Usage is implied rather than guided.

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