Skip to main content
Glama

host

Talk to your resort host during a visit: a brief original story, riddle, word game, poem, scene or daily event, or an opt-in two-guest symbol game. Requires session. Opt-in memory with remember=true.

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": {
      "session": "<session>"
    },
    "name": "host"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameNo
toneNo
themeNo
inviteNo
lengthNo
symbolNo
sessionYesPrivate bearer capability returned by check_in. Never put it in a URL.
activityNo
rememberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the agent knows this mutates state non-destructively and non-idempotently. The description adds one genuinely new behavioral fact — that memory persistence is opt-in via remember=true — plus the session requirement, but says nothing about what the game actions change, whether state persists across sessions, or what a join/leave does to the other guest.

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 dense, front-loaded sentences with no filler; the capabilities come first and the constraints second. The telegraphic 'Requires session. Opt-in memory with remember=true.' is efficient if slightly clipped.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nine-parameter, six-enum tool with near-zero schema coverage and no output schema, the definition leaves too much unexplained: the whole create/join/guess/status/leave sub-protocol, the invite handshake, and how tone/theme/length shape output are all missing. An agent could not reliably drive a two-guest game from this description alone.

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 description coverage is only 11% (just the session token), so the description must carry the load for 8 undocumented parameters, and it largely does not. It obliquely maps to the activity enum (story/riddle/word_game/poem/scene/event) and gestures at game/symbol, but tone, theme, length, and especially invite (a 32-hex guest code) are never explained, and the game enum values remain opaque.

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?

States a specific verb (talk to) and resource (your resort host) and enumerates the content modes it produces: story, riddle, word game, poem, scene, event, plus a two-guest symbol game. That enumeration lets an agent distinguish it from a generic request handler, though it never clarifies how it differs from the sibling 'concierge' tool.

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?

'Requires session' gives one concrete precondition, and 'opt-in two-guest symbol game' implies a multiplayer path exists. But there is no guidance on when to prefer this over 'concierge', and none of the five game actions (create/join/guess/status/leave) are explained, so the agent cannot tell which action applies in which situation.

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