Skip to main content
Glama

Stop the journey

stop_traveler_journey

Halt the virtual traveler’s journey on the Map Traveler MCP server. Use this tool to pause or end the avatar’s movement, stopping photo reports and SNS updates during mapped travels.

Instructions

Stop the traveler's journey

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Primary handler: Stops the journey by calculating current position, resetting run status to 'stop', generating location view with facilities and image, and saving the updated status.
    function stopJourney(practice: boolean) {
      return Effect.gen(function* () {
        const now = dayjs()
        const {runStatus} = yield* getRunStatusAndUpdateEnd(now)
        if (runStatus.status === "stop") {
          return yield* Effect.fail(new AnswerError(`The journey has already arrived in "${runStatus.to}".`));
        }
        let res
        if (practice) {
          res = yield* getFacilitiesPractice(runStatus.to, true).pipe(Effect.andThen(a => runningReport(a.locText, a.nearFacilities, a.image, true)))
        } else {
          const runnerEnv = yield* DbService.getSysEnv()
          const elapse = Math.min(now.diff(runStatus.startTime, "seconds") / dayjs.unix(runStatus.tilEndEpoch).diff(runStatus.startTime, "seconds"), 1)
          const currentInfo = yield* calcCurrentLoc(runStatus, elapse); //  これは計算位置情報
          const nears = yield* StoryService.getNearbyFacilities({
            lat: currentInfo.lat,
            lng: currentInfo.lng,
            bearing: currentInfo.bearing
          })
    
          resetRunStatus(runStatus, Option.getOrElse(nears.address, () => runStatus.to), now.toDate(),
            currentInfo.lat, currentInfo.lng, Option.getOrElse(nears.country, () => runStatus.endCountry), currentInfo.timeZoneId)
    
          res = yield* getFacilities(currentInfo, runnerEnv, true, false).pipe(Effect.andThen(a => runningReport(a.locText, a.nearFacilities, a.image, true)))
        }
    
        runStatus.to = Option.getOrElse(res.address, () => runStatus.from)
        yield* DbService.saveRunStatus(runStatus)
        return res.out
      })
    }
  • Tool dispatch in switch statement: Maps 'stop_traveler_journey' (and alias) to local stopJourney function.
    case "stop_journey":
    case "stop_traveler_journey":
      return stopJourney(env)
  • Tool schema definition: Specifies name (conditional on personMode), title, description, and empty input schema.
    {
      name: env.personMode === 'second' ? "stop_journey" : "stop_traveler_journey",
      title: "Stop the journey",
      description: env.personMode === 'second' ? "Stop the journey" : "Stop the traveler's journey",  //  停泊と合わせて停止シーン画像を取得して添付する
      inputSchema: {
        type: "object",
        properties: {},
      }
    },
  • Tool registration: Adds START_STOP_COMMAND (containing stop_traveler_journey) to the tools list in makeToolsDef when not in skip mode.
      cmd.push(...START_STOP_COMMAND)
    }
  • Local wrapper: Delegates to RunnerService.stopJourney with practice flag from env.
    const stopJourney = (env:Mode) => {
      return RunnerService.stopJourney(env.isPractice)
    }
Behavior1/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 of behavioral disclosure. 'Stop the traveler's journey' implies a mutation or state change, but the description doesn't specify whether this action is reversible, what permissions are required, what side effects occur (e.g., does it cancel ongoing processes?), or what the response looks like. This is inadequate for a tool that likely alters system state.

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 description is a single, concise sentence with no wasted words, which is efficient. However, it's under-specified rather than appropriately sized—it lacks necessary context for a mutation tool, so its brevity doesn't earn full credit for being 'front-loaded' with helpful information.

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 likely performs a mutation (stopping a journey) with no annotations and no output schema, the description is incomplete. It doesn't explain what 'stopping' entails, what happens post-execution, or any error conditions, leaving significant gaps for an agent to understand the tool's behavior and outcomes.

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 with 100% schema description coverage, so the schema fully documents the absence of inputs. The description doesn't need to add parameter details, and it correctly implies no parameters are required by not mentioning any. This meets the baseline for zero-parameter tools.

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

Purpose2/5

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

The description 'Stop the traveler's journey' is a tautology that merely restates the tool name 'stop_traveler_journey' and title 'Stop the journey' without adding specificity. It doesn't clarify what 'journey' means in this context or what resources are affected, though it does include the verb 'stop' and resource 'traveler's journey' which provides minimal differentiation from siblings like 'start_traveler_journey'.

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. It doesn't mention prerequisites (e.g., that a journey must be active), exclusions, or comparisons to sibling tools like 'start_traveler_journey', leaving the agent with no contextual usage information beyond the tool's name.

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