Skip to main content
Glama

travel_to_location

Move a party to a point of interest on the world map, automatically discovering it if needed and optionally entering its entrance room.

Instructions

Move a party to a POI on the world map. Combines move_party + discover_poi + enter_room.

TOKEN SAVINGS: ~70% vs separate calls (3 tools → 1)

WHAT THIS TOOL DOES:

  1. Moves party to POI coordinates on world map

  2. Auto-discovers the POI if not yet discovered (with perception check if DC set)

  3. Optionally enters the POI's entrance room if it has a network

Example - Travel to known location: { "partyId": "party-1", "poiId": "poi-tavern-1" }

Example - Travel and auto-enter dungeon: { "partyId": "party-1", "poiId": "poi-dungeon-1", "enterLocation": true }

Example - Travel with discovery bypass: { "partyId": "party-1", "poiId": "poi-hidden-temple", "autoDiscover": true }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
partyIdYesParty ID to move
poiIdYesPOI ID destination
enterLocationNoIf true and POI has a room network, move party leader into entrance room
autoDiscoverNoIf true, skip perception check for undiscovered POIs
discoveringCharacterIdNoCharacter making discovery check (defaults to party leader)
sessionIdNo
Behavior4/5

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

With no annotations provided, the description carries full burden and does well: it explains the multi-step behavior (move + auto-discover + optional enter), mentions a perception check condition ('if DC set'), and describes what happens with different parameter combinations through concrete examples. It doesn't cover error cases or rate limits, but provides substantial behavioral context.

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?

The description is efficiently structured with clear sections: purpose statement, token savings rationale, numbered what-it-does list, and concrete examples. Every sentence adds value—no fluff or repetition. It's appropriately sized for a complex 6-parameter tool.

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 complex mutation tool with 6 parameters, no annotations, and no output schema, the description does well: it explains the multi-step behavior, provides usage guidance vs siblings, and shows parameter interactions. It could mention error conditions or return values, but given the schema coverage and examples, it's mostly complete for agent use.

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 description coverage is high (83%), so baseline is 3. The description adds value beyond the schema by explaining parameter interactions through examples: it shows how 'enterLocation' works with dungeon POIs, how 'autoDiscover' bypasses perception checks, and implies 'discoveringCharacterId' defaults to party leader. This provides practical context not in the schema descriptions.

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 explicitly states the tool's purpose as 'Move a party to a POI on the world map' and distinguishes it from siblings by explaining it 'Combines move_party + discover_poi + enter_room' (two of which are sibling tools: move_party and discover_poi is implied). It provides specific verb+resource+scope differentiation.

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?

The description provides explicit guidance on when to use this tool vs alternatives: it states it combines three separate tools (move_party, discover_poi, enter_room) and offers 'TOKEN SAVINGS: ~70% vs separate calls (3 tools → 1)', clearly positioning it as a consolidated alternative to those sibling operations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Mnehmos/mnehmos.rpg.mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server