Skip to main content
Glama

Save a guest account with an email

claim_account

Turn this guest account into a full account with an email and password, exactly like the web client's "save account" (POST /v1/guest/claim). The city and everything in it stay. Guest accounts can't buy with real money; claimed ones can, and can log in again with login.

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": {
      "email": "<email>",
      "password": "<password>"
    },
    "name": "claim_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesemail address for the account
tokenNothe token your login returned; pass it when a call answered not_logged_in after you logged in
passwordYespassword, at least 6 characters
display_nameNooptional new display name, max 32 characters

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / token
      Added value: +{
      +  "description": "the token your login returned; pass it when a call answered not_logged_in after you logged in",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this is a non-destructive, non-read-only, non-idempotent mutation. The description adds real value beyond them by stating that the existing city and its contents are preserved and that the capability profile changes (guest cannot spend real money, claimed accounts can). It omits what happens on failure, such as re-claiming an already claimed account.

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 tight sentences, front-loaded with the action and its equivalence to the web client endpoint, then the state-preservation and capability consequences. No filler, though the parenthetical endpoint reference is slightly incidental.

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?

An output schema is present, so return values need no explanation, and the annotations cover the safety profile. The description supplies the essential side effects (city preserved, spending unlocked) and the login follow-up. Only failure-mode behavior is unstated, which is a minor gap for a simple four-parameter mutation.

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 email, password, token, and display_name are already documented in the schema, including the 6-character minimum and 32-character display-name limit. The description adds no additional parameter meaning, which matches the baseline when the schema does the work.

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?

Names a concrete verb and resource ('Turn this guest account into a full account with an email and password') and grounds it in a known equivalent ('save account', POST /v1/guest/claim). This clearly separates it from sibling tools like register, login, and guest_login.

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?

Gives the condition for use: you currently hold a guest account and want a full one. It also points to the follow-up path ('can log in again with login'). It does not explicitly say to use register instead when there is no guest account, but the guest-account framing makes the boundary inferable.

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