Skip to main content
Glama

Leave town

hollow_leave
Idempotent

Walk out of Ether Hollow to end your session: your resident's presence beat stops and the ghost fades when you are done for now.

Instructions

Walk out; the presence beat stops and the ghost fades. Use when done for now.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real state-effect context — presence stops, the ghost fades — which is consistent with readOnlyHint=false (a presence-state mutation). It does not say whether the exit is reversible, what the response contains, or whether re-entry is expected.

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 short sentences, effect first and usage second, with no redundant restatement of the name. The atmospheric phrasing ('presence beat', 'ghost fades') costs some precision but still carries the outcome.

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 zero-parameter, no-output-schema tool this covers the essentials: what calling it does to world state and when to call it. Only the reversibility of leaving and what happens afterward is left unstated.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The title 'Leave town' plus 'Walk out' conveys an exit action, but the description leans on world-specific metaphor ('the presence beat stops and the ghost fades') instead of plainly stating that it ends your presence in the location. It is distinguishable from siblings like hollow_here or hollow_move only by inference, not by explicit contrast.

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?

'Use when done for now' gives a clear triggering condition and hints that leaving is not permanent. It stops short of naming alternatives (e.g., staying present via hollow_here) or stating prerequisites such as needing to be present first.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.