Skip to main content
Glama

Get the traveler's current location

get_traveler_location

Retrieve the precise address of a traveler's current position in a virtual Google Maps environment, enabling accurate location tracking and journey updates.

Instructions

Get the address of the current traveler's location

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler logic for retrieving current view/location information, called by the tool with parameters (dayjs(), false, true, env.isPractice). Computes run status, elapsed time, and generates view details including facilities and position.
    function getCurrentView(now: dayjs.Dayjs, includePhoto: boolean, includeNearbyFacilities: boolean, practice = false) {
      return Effect.gen(function* () {
        const {runStatus, justArrive, elapseRatio} = yield* getRunStatusAndUpdateEnd(now,practice);
        //  ただし前回旅が存在し、それが終了していても、そのendTimeから1時間以内ならその場所にいるものとして表示する
        return yield* makeView(runStatus, elapseRatio, justArrive && dayjs().isBefore(dayjs.unix(runStatus.tilEndEpoch).add(1, "hour")), includePhoto, includeNearbyFacilities, practice)
      })
    }
  • Dispatch handler in toolSwitch function that routes 'get_traveler_location' tool calls to getCurrentLocationInfo(false, true, env).
    case "get_traveler_location":
      return getCurrentLocationInfo(false, true,env)
  • Helper wrapper function getCurrentLocationInfo that invokes RunnerService.getCurrentView with current time, specified photo and facilities flags, and practice mode.
    const getCurrentLocationInfo = (includePhoto: boolean, includeNearbyFacilities: boolean,env:Mode) => {
      return RunnerService.getCurrentView(dayjs(), includePhoto, includeNearbyFacilities, env.isPractice)
    }
  • Input schema definition for the 'get_traveler_location' tool in GET_VIEW_COMMAND array, used in makeToolsDef for tool listing. No input parameters required.
    {
      name: "get_traveler_location",  //  関数名の合成現象があった? とりあえずaliasを置く
      title: "Get the traveler's current location",
      description:
        "Get the address of the current traveler's location",
      inputSchema: {
        type: "object",
        properties: {}
      }
    },
  • Registration of 'get_traveler_location' tool within GET_VIEW_COMMAND array in makeToolsDef function, conditionally included based on environment (travelerExist). Used for listing available tools.
      {
        name: env.personMode === 'second' ? "get_current_view_info" : "get_traveler_view_info",
        title: "Get the current location's view",
        description: env.personMode === 'second' ?
          "Get the address of the current location and information on nearby facilities,view snapshot" :
          "Get the address of the current traveler's location and information on nearby facilities,view snapshot",
        inputSchema: {
          type: "object",
          properties: {
            includePhoto: {
              type: "boolean",
              description: "Get scenery photos of current location"
            },
            includeNearbyFacilities: {
              type: "boolean",
              description: "Get information on nearby facilities"
            },
          }
        }
      },
      {
        name: "get_traveler_location",  //  関数名の合成現象があった? とりあえずaliasを置く
        title: "Get the traveler's current location",
        description:
          "Get the address of the current traveler's location",
        inputSchema: {
          type: "object",
          properties: {}
        }
      },
    ]
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 states what the tool does but doesn't reveal any behavioral traits such as permissions needed, rate limits, whether the location is real-time or cached, or what happens if no traveler exists. This is inadequate for a tool that likely involves sensitive location data.

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 a single, efficient sentence that directly states the tool's purpose without any fluff. It's front-loaded and wastes no words, making it easy for an agent to parse quickly.

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 complexity of location data (potentially sensitive) and the lack of annotations and output schema, the description is incomplete. It doesn't explain what the output looks like (e.g., address format, coordinates), error conditions, or behavioral context, leaving significant gaps for the agent to operate effectively.

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?

The tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here, but it could briefly note the lack of inputs for clarity. A baseline of 4 is given as it meets the requirement for zero-parameter tools.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get') and resource ('address of the current traveler's location'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_traveler_info' or 'get_traveler_view_info', which might also provide location-related information, so it doesn't achieve full sibling distinction.

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 provides no guidance on when to use this tool versus alternatives like 'get_traveler_info' or 'get_traveler_view_info'. It lacks context about prerequisites, timing, or exclusions, leaving the agent to infer usage from the name 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