Skip to main content
Glama

Get the traveler's preferences (optional).

get_traveler_info

Retrieve traveler details such as name, language, personality, and speaking habits to customize interactions in the Map Traveler MCP virtual journey environment.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
settingsNo

Implementation Reference

  • The handler function that retrieves the traveler's information ('aiEnv') from the database and returns it as a text content block, or a default message if not set.
    const getTravelerInfo = () => {
      return DbService.getEnv('aiEnv').pipe(
        Effect.andThen(a => [{
            type: "text",
            text: `The traveller's information is as follows: ${a}`
          } as ToolContentResponse]
        ),
        Effect.orElseSucceed(() => [{
            type: "text",
            text: `There is no traveler information.`
          } as ToolContentResponse]
        )
      )
    }
  • Tool definition and registration in the SETTING_COMMANDS array used by makeToolsDef for listing tools, includes name, title, description, and input schema.
      name: "get_traveler_info",
      title: "Get the traveler's preferences (optional).",
      description: "get a traveler's setting.For example, traveler's name, the language traveler speak, Personality and speaking habits, etc.",
      inputSchema: {
        type: "object",
        properties: {
          settings: {},
        }
      }
    },
  • Dispatch case in toolSwitch function that maps the tool call to the getTravelerInfo handler.
    case "get_traveler_info":
      return getTravelerInfo()
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 but only mentions what data is retrieved without disclosing behavioral traits like permissions needed, rate limits, or response format. It lacks details on whether this is a read-only operation or has other constraints.

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, using a single sentence with examples to convey the purpose efficiently. However, it could be more structured by explicitly stating the tool's scope or limitations.

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 1 undocumented parameter, no annotations, and no output schema, the description is incomplete. It provides basic purpose but lacks details on parameters, behavior, and output, making it inadequate for effective tool use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 1 parameter with 0% description coverage, and the tool description does not explain the 'settings' parameter at all. It fails to add any meaning beyond the schema, leaving the parameter undocumented and unclear in usage.

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 retrieves a traveler's settings with examples (name, language, personality), which clarifies the purpose beyond the name. However, it doesn't differentiate from sibling tools like 'get_setting' or 'get_traveler_view_info', making it somewhat vague in comparison.

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?

No guidance is provided on when to use this tool versus alternatives such as 'get_setting' or 'get_traveler_view_info'. The description only lists examples of what it retrieves, offering no context for selection among siblings.

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