Skip to main content
Glama

plan_contemplative_journey

Read-onlyIdempotent

Get curated places and a paced day-by-day itinerary when available, with a link to the web planner.

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>"
    },
    "name": "plan_contemplative_journey"
  }
}

Input Schema

NameRequiredDescriptionDefault
originNoOrigin city or airport code (e.g., Bogota, Madrid, NYC, BOG, MAD)
languageNoThe traveler's language: en, es or pt (any other language -> en)en
destinationYesDestination city or region (e.g., Rome, Paris, CDMX, Tokyo, Kyoto, Barcelona, Lisbon, London, Bogota, Medellin, New York, Miami)
duration_daysNoDuration of stay in days (1-7)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the bar is lower. The description adds useful behavior beyond that: itineraries are returned only 'when available' (partial coverage expected) and a web planner link is included in the response. It still says nothing about whether origin or duration_days materially change results.

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?

A single front-loaded sentence with no filler; the return contents are stated before the parenthetical detail. Nothing is redundant with the title or schema.

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

Completeness3/5

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

For a read-only four-parameter tool with no output schema, the description adequately sketches the response shape (places, itinerary, planner link). It is incomplete on how origin and language affect the output and offers no selection guidance against siblings, both of which matter for a discovery-style tool.

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

Parameters3/5

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

Schema description coverage is 100% with examples and defaults for all four parameters, so the schema does the heavy lifting. The description references 'paced day-by-day' which loosely implies duration_days influences pacing, but it adds no format, constraint, or semantics beyond the schema.

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 names a specific verb-resource pair — retrieving curated places plus a paced day-by-day itinerary and a link to the web planner — so the agent knows what comes back. It does not differentiate itself from siblings with similar discovery framing (discover_secret_haven, explore_sensory_earth), leaving overlap ambiguous.

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?

There is no statement of when to use this tool versus the sibling discovery/booking tools, and no prerequisites or context given. The only usage-adjacent signal is the hedge 'when available', which hints at partial results but does not guide tool selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources