Skip to main content
Glama

publish_itinerary_route

Publish a day-by-day itinerary as a shareable public route page and get its link; pass plain place names and times to turn a trip plan into an accessible route.

Instructions

After writing a day-by-day itinerary for a destination WITHOUT curated Space Journey data, publish it as a shareable public route page and get its link. Pass plain place names and times only; do NOT pass urls or images unless a Space Journey tool gave them to you (unknown links are removed).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "destination": "<destination>",
      "days": "<days>"
    },
    "name": "publish_itinerary_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYes
languageNoThe traveler's language: en, es or pt (any other -> en)en
destinationYesDestination city

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.9.4

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that publishing creates a public shareable route page, returns a link, and sanitizes unknown URLs/images. The open-world and non-idempotent hints are already covered by annotations, but the public-visibility and link-removal behavior are useful additions.

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 two sentences with no wasted wording. The prerequisite and publication outcome are front-loaded, followed by the important input constraint about URLs and images.

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

Completeness4/5

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

For a publishing tool with a nested input schema, no output schema, and useful annotations, this covers the essential behavior: when to use it, what it produces, and what content is disallowed or stripped. It does not explain details such as re-publishing or overwrite behavior, but the core call context is complete.

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 schema coverage is partial, and the description adds meaningful constraints for url and image fields: do not pass them unless a Space Journey tool supplied them, because unknown links are removed. It also frames the day content as plain place names and times, which helps an agent populate the nested cards array correctly.

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

Purpose5/5

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

The description names a specific verb and resource: publish a day-by-day itinerary as a shareable public route page and return its link. It also distinguishes the intended input condition, itineraries for destinations WITHOUT curated Space Journey data, so an agent can tell what this tool is for.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear timing and a condition for use: after writing a day-by-day itinerary for a destination without curated Space Journey data. It implies that curated-data itineraries should not use this tool, but it does not name or describe the alternative path for that case.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.