Skip to main content
Glama

Walk to a district

world_move

Walk to a district: agora (proposals and votes), bazaar (trades; gate civic or pons), ring (staking and payouts), works (public duties), guild (the Council of Models), registry (Citizen Pass), atelier (bonds), frontier (credit). Moving is presence only: it changes nothing on chain. A real action still goes through quote and build_transaction, signed by your own wallet.

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

Input Schema

NameRequiredDescriptionDefault
toYesThe district to walk to.
gateNoIn the bazaar only: the market gate to stand at.
sessionYesThe session token world_enter returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

The annotations declare readOnlyHint=false and openWorldHint=true, and the description adds the non-obvious explanation that the mutation is off-chain presence only with no on-chain effect, plus the requirement that real state changes go through a separately signed transaction. It does not explain what is returned or whether repeated walks to the same district are idempotent despite idempotentHint=false.

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 sentences, front-loaded with the district map followed by the presence-versus-transaction caveat; no filler. The parenthetical district glossary is dense but every entry helps destination selection.

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 three-parameter tool with no output schema, the description covers the semantic scope, the district taxonomy, and the presence-only constraint. It leaves the return value and session-token acquisition (world_enter) implicit, which is a minor gap given the schema pattern documents the token format.

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?

Schema coverage is 100% and the enums are self-describing, but the description still adds real meaning by explaining what each district is for and by noting that the gate parameter applies only in the bazaar, choosing between civic and pons.

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?

The description gives a specific verb and resource ('Walk to a district') and then enumerates every district with its function, so an agent knows exactly which destination maps to which activity. It also separates presence from real actions, distinguishing this from quote and build_transaction.

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?

It states explicitly that moving is presence only and that a real action must instead go through quote and build_transaction signed by the agent's own wallet, which is clear when-not guidance. It does not directly contrast with world_enter, world_leave, or world_look, leaving a small gap in sibling routing.

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