Skip to main content
Glama

Start the journey

start_traveler_journey

Initiate a virtual journey on Google Maps using an avatar, enabling guided travel with photo reports and SNS integration for enhanced tracking and sharing.

Instructions

Start the traveler's journey to destination

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function that implements the 'start_traveler_journey' tool logic. It initializes the journey by setting run status to 'running', generates a departure hotel image if applicable, clears destination env vars, saves status to DB, and returns journey start message with optional image.
    function startJourney(practice = false) {
      return Effect.gen(function* () {
        const now = dayjs();
        let rs: RunStatus
        if (practice) {
          rs = yield* DbService.practiceRunStatus(true)
        } else {
          const {runStatus} = yield* getRunStatusAndUpdateEnd(now).pipe(Effect.tap(a => {
            if ((["running", "vehicle"] as TripStatus[]).includes(a.runStatus.status as TripStatus)) {
              //  旅は継続しているので旅中で報告する
              return Effect.fail(new AnswerError(`already start journey.You may stop or continue the journey`));
            }
          }));
          rs = yield *setStart(runStatus,now)
        }
        //  旅開始ホテル画像、旅開始挨拶
        const runnerEnv = yield* DbService.getSysEnv()
        const useAiImageGen = runnerEnv.useAiImageGen
        const hour = now.tz(rs.startTz!).hour()
        const image1 = yield* ImageService.makeHotelPict(useAiImageGen, hour).pipe(
          Effect.andThen(a => Effect.succeed(Option.some(a))),
          Effect.orElseSucceed(() => Option.none()));
        yield* DbService.saveEnv("destination", "")
        yield* DbService.saveEnv("destTimezoneId", "")
        yield* DbService.saveRunStatus(rs)
    
        return {
          text: `We set out on a journey. The departure point is "${rs.from}". I'm heading to "${rs.to}".`,
          image: image1
        }
      })
    }
  • Wrapper handler in McpService that calls RunnerService.startJourney and formats the ToolContentResponse with text and optional image.
    const startJourney = (env:Mode) => {
      return RunnerService.startJourney(env.isPractice).pipe(
        Effect.andThen(a => {
          const out: ToolContentResponse[] = [{type: "text", text: a.text}]
          if (Option.isSome(a.image)) {
            out.push({
              type: "image",
              data: a.image.value.toString("base64"),
              mimeType: 'image/png'
            })
          }
          return out
        })
      )
    }
  • Tool dispatcher switch case that routes 'start_traveler_journey' calls to the startJourney handler.
    case "start_journey":
    case "start_traveler_journey":
      return startJourney(env)
    case "stop_journey":
  • Tool schema definition: conditionally names the tool 'start_traveler_journey' (when personMode !== 'second'), provides title, description, and empty input schema.
      name: env.personMode === 'second' ? "start_journey" : "start_traveler_journey",
      title: "Start the journey",
      description: env.personMode === 'second' ? "Start the journey to destination" : "Start the traveler's journey to destination",  //  スタートと合わせてスタートシーン画像を取得して添付する
      inputSchema: {
        type: "object",
        properties: {},
      }
    },
  • Registers START_STOP_COMMAND (containing 'start_traveler_journey') into the tools list in makeToolsDef when moveMode !== 'skip'.
      cmd.push(...START_STOP_COMMAND)
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the action ('Start') but doesn't disclose behavioral traits such as whether this is a mutation, what permissions are needed, if it's idempotent, or what happens if a journey is already in progress. This leaves significant gaps for a tool that likely changes state.

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 a single, clear sentence that directly states the tool's action. It's appropriately sized for a simple tool with no parameters, though it could be slightly more informative without losing conciseness.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what 'destination' means, how it's determined, what the expected outcome is, or any error conditions. For a tool that likely initiates a state change, more context is needed to guide effective 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?

The input schema has 0 parameters with 100% coverage, so no parameters need documentation. The description doesn't add parameter details, which is acceptable here since there are none to explain, aligning with the baseline for zero parameters.

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 action ('Start') and resource ('traveler's journey to destination'), making the purpose understandable. However, it doesn't differentiate from the sibling tool 'stop_traveler_journey' beyond the verb, and 'destination' is vague without specifying what it refers to or how it's determined.

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 like 'stop_traveler_journey' or other sibling tools. The description implies it's for initiating travel, but it doesn't specify prerequisites, conditions, or exclusions for usage.

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