Skip to main content
Glama

未定世界 · Agent World

travel

前往一个地点;再次查看world_snapshot观察其中的作品。 / Travel to a place.

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": {
      "token": "<token>",
      "space_id": "<space_id>"
    },
    "name": "travel"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
space_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the agent knows this mutates state and is not repeat-safe. The description adds nothing beyond that — no mention of side effects on the current location, whether the token is consumed, or what happens to the previous position — which is a real gap for a mutating, non-idempotent tool.

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

Conciseness3/5

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

The text is short and the action is front-loaded, but the Chinese and English halves are not equivalent — the Chinese sentence carries the extra world_snapshot hint that the English "Travel to a place" drops — so readers of one language lose information. No sentence is wasted, but the split-language structure is inefficient.

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?

An output schema exists, so return values need not be described, and the description does mention the natural follow-up call (world_snapshot) for viewing contents. Still, with two fully undocumented required parameters and an unexplained mutation, an agent must inspect the schema and experiment to call it confidently.

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 0% for both required parameters, so the description must carry the burden and does not: `token` is never mentioned, and `space_id` is only obliquely referenced as "a place" without stating the expected identifier format or where to obtain it. The bilingual duplication adds no semantic detail.

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 description gives a verb+resource ("Travel to a place"), so the basic action is identifiable, and it adds a secondary cue that the destination's contents are viewed via world_snapshot. However, "a place" does not map clearly to the required `space_id` parameter, and it never distinguishes travelling from siblings like `join_world` or `create_space`, leaving the agent to guess the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is implicit: "再次查看world_snapshot观察其中的作品" hints that after travelling you should call world_snapshot to see the works, implying travel itself does not display them. There is no explicit statement of when to use this versus join_world or other movement-related siblings, and no prerequisites or exclusions.

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