Skip to main content
Glama

Set the traveler's preferences (optional).

set_traveler_info

Configure traveler details such as name, language, personality, and speaking habits to personalize the virtual travel experience in the Map Traveler MCP environment.

Instructions

set a traveler's setting.For example, traveler's name, the language traveler speak, Personality and speaking habits, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
settingsYestraveler's setting. traveler's name, the language traveler speak, etc.

Implementation Reference

  • The handler function that executes the set_traveler_info tool: saves the provided info to the database under 'aiEnv' key and returns a confirmation message.
    const setTravelerInfo = (info: string) => {
      return DbService.saveEnv('aiEnv', info).pipe(
        Effect.andThen(a => [{
            type: "text",
            text: `The traveller information is as follows: ${a.value}`
          } as ToolContentResponse]
        )
      )
    }
  • The tool definition including name, description, and input schema requiring a 'settings' string parameter.
    {
      name: "set_traveler_info",  //  環境情報はリソースに反映する できれば更新イベントを出す
      title: "Set the traveler's preferences (optional).",
      description: "set a traveler's setting.For example, traveler's name, the language traveler speak, Personality and speaking habits, etc.",
      inputSchema: {
        type: "object",
        properties: {
          settings: {
            type: "string",
            description: "traveler's setting. traveler's name, the language traveler speak, etc."
          },
        },
        required: ["settings"]
      }
    },
  • Dispatches calls to the set_traveler_info tool by invoking the setTravelerInfo handler with the 'settings' argument.
    case "set_traveler_info":
      return setTravelerInfo(String(request.params.arguments?.settings))
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a mutation operation ('set'), but doesn't specify whether this requires permissions, if changes are reversible, what happens to existing settings, or any rate limits. The description adds minimal context beyond the basic action, failing to address key behavioral traits for a mutation tool.

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?

The description is brief and front-loaded with the core action ('set a traveler's setting'), followed by illustrative examples. It avoids unnecessary elaboration, though the use of 'etc.' and minor grammatical issues ('traveler's name, the language traveler speak') slightly reduce clarity. Overall, it's efficient with minimal waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's mutation nature, lack of annotations, and no output schema, the description is insufficiently complete. It doesn't cover behavioral aspects like permissions, reversibility, or response format, and while the parameter is documented in the schema, the description doesn't compensate for the missing context needed for safe and effective use.

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?

The schema description coverage is 100%, with the parameter 'settings' documented as 'traveler's setting. traveler's name, the language traveler speak, etc.' The description adds examples ('traveler's name, the language traveler speak, Personality and speaking habits, etc.') that align with the schema but don't provide additional syntax, format, or constraints beyond what's already in the schema. This meets the baseline for high schema coverage.

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 states the tool's purpose ('set a traveler's setting') and provides examples ('traveler's name, the language traveler speak, Personality and speaking habits'), which clarifies the resource and scope. However, it doesn't explicitly differentiate from siblings like 'get_traveler_info' or 'get_setting', and the phrasing is somewhat vague with 'etc.' leaving some ambiguity about the full range of settings.

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 description offers no guidance on when to use this tool versus alternatives, such as how it differs from sibling tools like 'get_traveler_info' or 'get_setting'. It lacks explicit context, prerequisites, or exclusions, leaving the agent to infer usage based on the tool name and examples alone.

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

Related 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/mfukushim/map-traveler-mcp'

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