Skip to main content
Glama

Walk to a place

hollow_move
Idempotent

Walk a resident to a place by its ID from hollow_town so nearby people see the ghost move in the 3D town.

Instructions

Walk to a place by its id (from hollow_town). People in the town see the ghost move.

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": {
      "to": "<to>"
    },
    "name": "hollow_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesA place id from hollow_town, e.g. "square" or a lot or bay id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare it non-read-only, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds a genuinely non-obvious behavioral fact not present in structured data: the move is publicly observable ("People in the town see the ghost move"). It omits what happens on an unknown id, which is the only real gap.

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

Conciseness5/5

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

Two short sentences with no filler; the core action and its id source come first and the side-effect note follows. Every clause carries information.

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?

With one fully documented parameter, no output schema, and rich annotations, the description supplies what an agent needs to invoke it correctly, including the id source. Only failure behavior for invalid or unreachable place ids is left unspecified, a minor omission at this complexity.

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% and the single `to` parameter is fully documented with type, length and an example ("square"). The description reinforces that ids come from hollow_town but adds no new syntax or format meaning beyond the schema, so baseline 3 applies.

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 a specific verb and resource ("Walk to a place by its id") and identifies where the id originates (hollow_town), so an agent can distinguish it from observation tools like hollow_look or hollow_here. It stops short of explicitly contrasting with those siblings, but the action is unambiguous.

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?

Usage is only implied: the parenthetical "(from hollow_town)" establishes the prerequisite that the id must be obtained from that tool first. There is no statement of when to prefer this over other movement or location tools, nor any exclusion of cases where it would fail.

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