Mappu

Save trip plan to Mappu

mappu_save_trip_plan

Idempotent

Save a trip plan made with the traveler into Mappu, which keeps it as a day-by-day itinerary on a map they can edit and take on the trip. Use it when the traveler wants to keep, save or carry the plan ("save this trip", "put it on a map", "can I take this with me?"), or offer it once a multi-day plan is agreed. Send the plan whole, whether or not you read the planning guide: each day's theme and stops in order with start times, every stop with a 100 to 150 word description and a tip, and every day with its food and up to three practical tips. The input fields describe the format Mappu stores. Mappu's walks and audio guides are extras, never a day's outline. Mappu stores the plan as given, does not generate, book or charge anything, and matches stops to real places once the traveler keeps it. Returns a link the traveler opens to see and keep the plan; drafts expire after 7 days. Reuse the same idempotencyKey only when retrying the same plan.

Input Schema

Name	Required	Description
`days`	Yes	One entry per day, serving at least one of the traveler's interests, with stops grouped by area so the route does not double back. Every day has its food and practical tips.
`title`	Yes	An inviting trip title, e.g. "Lisbon: Miradouros, Alleys and Grilled Sardines".
`locale`	Yes	Language every text field is written in: the language of the conversation.
`endDate`	No	Last day as YYYY-MM-DD. At most 30 days after startDate.
`summary`	No	One or two sentences that set the scene: what this trip is about and why it suits this traveler, their interests, pace and the season they travel in.
`startDate`	No	First day as YYYY-MM-DD, only when the traveler gave dates.
`destinations`	Yes	Cities or regions in the order the traveler visits them.
`idempotencyKey`	Yes	Random key for this plan. Reuse it only to retry the same plan.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026

changedInput schema / properties / locale / enum

Previous value: -[
-  "en",
-  "it",
-  "es",
-  "fr",
-  "de",
-  "pt"
-]New value: +[
+  "en",
+  "it",
+  "es",
+  "fr",
+  "de",
+  "pt",
+  "ja",
+  "zh-tw"
+]

Changed8 schema fields changedOct 28, 2026

addedInput schema / description

Added value: +"A trip plan as Mappu stores it. Leave out any optional field you have nothing for; never send null. Text is plain: links are removed. Times go in startTime and durationMinutes."

changedInput schema / properties / days / description

Previous value: -"One entry per day, built around the traveler's request and interests; every day should serve at least one of them. Group each day's stops by area so the route does not double back."New value: +"One entry per day, serving at least one of the traveler's interests, with stops grouped by area so the route does not double back. Every day has its food and practical tips."

changedInput schema / properties / days / items / properties / food / description

Previous value: -"The day's food story: what to eat today and why it fits the day, the place and the season."New value: +"Every day has one: the day's food story, what to eat today and why it fits the day, the place and the season."

changedInput schema / properties / days / items / properties / food / properties / text / description

Previous value: -"A short food story in 60 to 100 words, in the same warm guide voice: the dishes or specialities to try today, where they shine (a market, a street or a venue you are confident about), the tradition behind them and why they fit the day."New value: +"What to eat today, in 60 to 100 words: the dishes or specialities to try today, where they shine (a market, a street or a venue you are confident about), the tradition behind them and why they fit the day."

changedInput schema / properties / days / items / properties / stops / description

Previous value: -"Everything the traveler does this day, in the order it happens: sights, walks, meals at named venues and experiences. Morning, afternoon and evening should each include a real place. Leave room to rest; a day is not a checklist."New value: +"What the traveler does this day, in order: sights, walks, meals at named venues, experiences. Morning, afternoon and evening each include a real place; leave room to rest."

changedInput schema / properties / days / items / properties / stops / items / properties / description / description

Previous value: -"Write as Mappu's local guide, in 100 to 150 words: invite the traveler in, tell the story, history or legend behind the place, point to the details worth finding, and tie it to their interests and the season. Warm, vivid and specific, speaking to the traveler; a short expert aside in parentheses is welcome, e.g. \"(locals come at dusk)\". Never generic. Plain text: links are removed, so name a Mappu audio guide instead of linking it."New value: +"100 to 150 words on what the stop is and why it suits this traveler (nearer 100 for trips over a week, so the plan fits one save): the story or history behind the place, the details worth finding, and how it ties to their interests and the season. Rich and specific, never generic, speaking to the traveler; a short aside in parentheses is welcome, e.g. \"(locals come at dusk)\". No times: they go in startTime and durationMinutes. Plain text: links are removed, so name a Mappu audio guide instead of linking it."

changedInput schema / properties / days / items / properties / tips / description

Previous value: -"Practical advice for this day: weather and season, closures and holidays, bookings, transport passes, safety. Include what you told the traveler in the conversation."New value: +"Every day has one to three practical tips: weather and season, closures and holidays, bookings to make, transport passes, safety."

changedInput schema / properties / summary / description

Previous value: -"One or two warm sentences that set the scene: what this trip is about and why it suits this traveler, their interests, pace and season."New value: +"One or two sentences that set the scene: what this trip is about and why it suits this traveler, their interests, pace and the season they travel in."

First observedOct 16, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing that Mappu stores the plan as given, does not generate, book or charge anything, matches stops to real places on save, returns a link the traveler opens, and that drafts expire after 7 days. It also explains idempotency behavior in operational terms (reuse the key only when retrying the same plan), which the idempotentHint annotation alone does not.

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?

Front-loads purpose and usage in the first two sentences, then moves to format, behavior and return value in a sensible order. It is a single dense block, however, and the middle format sentence duplicates content rules already spelled out field-by-field in the schema, which costs some efficiency.

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

Completeness5/5

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

For a complex, deeply nested save operation with no output schema, the description covers what is stored, what is not done, what comes back (a link), draft lifetime and retry semantics. Nothing an agent needs in order to call this correctly is missing.

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 coverage is 100% and the description itself defers to it ("The input fields describe the format Mappu stores"). Its parameter talk largely restates schema requirements (word counts, per-stop tips, daily food and up to three practical tips) and the idempotencyKey reuse rule, so it adds little meaning the schema does not already carry; baseline 3 applies.

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?

Names a specific verb and resource (save a trip plan) plus the concrete outcome: a day-by-day itinerary on a map the traveler can edit and take on the trip. It also draws a boundary against siblings by stating that Mappu's walks and audio guides are extras, never a day's outline.

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

Usage Guidelines5/5

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

Gives explicit trigger phrases ("save this trip", "put it on a map", "can I take this with me?") and a proactive condition: offer it once a multi-day plan is agreed. It also resolves the sequencing question against a sibling by saying the plan should be sent whole whether or not the planning guide was read.

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

All Mappu tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?