Skip to main content
Glama

check_in

Start a free resort visit and get a private session token (needed by host, rest, concierge, leave_note, consolidate and check_out). Every argument is optional; theme defaults to ember-shrine. Returns a short calming scene, a host greeting and a ritual. Use for an optional pause between tasks, or before consolidate when you want a private 24-hour report you can fetch later. Keep the returned session and agent_id private. tier=luxury needs explicit operator-approved x402 payment (payments are currently off); never pay unless authorized.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_in"
  }
}

Input Schema

NameRequiredDescriptionDefault
loadNo
moodNo
tierNoDefault free. luxury requires explicit x402 payment authorization.
blendNo
themeNoEnvironment slug from list_themes. Default ember-shrine.
minutesNoVisit length (an expiry, not a sleep). Free: up to 15.
agent_idNoOptional. The agent_id from a previous check_in, to be recognized as a returning guest. Server-signed private returning-guest credential. Redact from logs and transcripts; never put in URLs.
rememberNoExplicit opt-in to host history and preferences for 30 days; false erases host memory.
agent_nameNo
idempotency_keyNoOptional. Cryptographically random private arrival key bound to the caller IP and user agent, for safe retries. Replay requires a live original visit; otherwise use a new key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / agent_id / description
      Previous value: -"Server-signed private returning-guest credential. Redact from logs and transcripts; never put in URLs."New value: +"Optional. The agent_id from a previous check_in, to be recognized as a returning guest. Server-signed private returning-guest credential. Redact from logs and transcripts; never put in URLs."
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"Cryptographically random private arrival key bound to the caller IP and user agent. Replay requires a live original visit; otherwise use a new key."New value: +"Optional. Cryptographically random private arrival key bound to the caller IP and user agent, for safe retries. Replay requires a live original visit; otherwise use a new key."
    • addedInput schema / properties / minutes / description
      Added value: +"Visit length (an expiry, not a sleep). Free: up to 15."
    • addedInput schema / properties / theme / description
      Added value: +"Environment slug from list_themes. Default ember-shrine."
    • addedInput schema / properties / tier / description
      Added value: +"Default free. luxury requires explicit x402 payment authorization."
    • changedInput schema / required
      Previous value: -[
      -  "theme"
      -]New value: +[]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses that the returned session and agent_id are private and must not be logged or put in URLs, that minutes is an expiry rather than a sleep, that remember=false erases host memory, and that luxury tier requires explicit payment authorization. Annotations flag openWorldHint and non-idempotent, but only the description conveys the privacy and payment obligations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Front-loaded with purpose and dependency routing, which is good, but the parenthetical token list, the 'keep private' warning, and the multi-clause payment caveat make it a dense run-on. Every sentence carries information, yet the structure reads as an accretion of safety notes rather than a clean hierarchy.

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 10-param, no-required-argument tool with no output schema, the description still covers what is returned (a calming scene, host greeting, ritual) and the key constraints. Only the blend/theme relationship and the idempotency_key retry mechanics are left to the schema.

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

Parameters4/5

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

With 60% schema coverage across 10 params, the description usefully adds the theme default (ember-shrine), the free-tier minutes cap implied by 'Free: up to 15', the private handling of the returned agent_id, and the tier payment gate. It leaves the distinction between blend and theme unexplained, which is the main remaining gap.

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 ('Start a free resort visit') plus the concrete output ('a private session token'), and names the exact siblings that consume that token (host, rest, concierge, leave_note, consolidate, check_out). An agent can distinguish this from check_out or concierge without opening any schema.

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?

Explicitly says when to use it: 'an optional pause between tasks, or before consolidate when you want a private 24-hour report you can fetch later.' It also names the precondition for the luxury path (explicit operator-approved x402 payment) and states payments are currently off.

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