Ourway – Camino de Santiago

Quote a Camino package (official Ourway price)

quote_camino_package

Read-only

Quote a complete Camino de Santiago trip as ONE all-in package price (hotels night by night with LIVE availability + pilgrim extras) — the source of the official Ourway package price. Use it whenever the user asks how much a Camino costs, wants a quote, or approves an itinerary from plan_camino_itinerary. It auto-selects the best accommodation for each night (Ourway quality filters: verified meal plan, close to the centre, guest rating) and returns a single total_paquete_eur. NEVER returns per-hotel, per-night or per-extra prices. presupuesto is REQUIRED (per person, whole trip, EUR): sin_preferencia | lt_500 | 500_1000 | 1000_1500 | gt_1500. meal_plan: RO | BB | HB | FB. categoria_alojamiento: recomendado | hoteles_encanto | casas_rurales | albergues. extras_ids from camino_extras_catalog (default: pilgrim credential + insurance; luggage transfer if incluir_mochila=true, one bag per traveller, priced by Ourway as bags × official stages of the Camino covered, so a day that spans two official stages counts two; pass the route's camino_slug from plan_camino_itinerary). ALWAYS pass nacionalidad (or residente_espana): it sets the insurance. mascotas=true when travelling with a pet. If a category has no availability one night the best alternative category is chosen (see avisos). Keep oferta_paquete_firmada verbatim for create_camino_booking_proposal. Usually 20-45 s (live checks hotel by hotel): tell the user it takes a moment. If your client times out, call it again with the SAME parameters: the result is cached and comes back instantly. / Fuente del precio oficial Ourway: un solo importe total del paquete, nunca precios parciales. Sin presupuesto no se cotiza. La mochila se calcula como bultos × etapas oficiales (un día que cubre dos etapas oficiales cuenta dos) y va dentro del total. Si tu cliente corta por timeout, repite la llamada con los mismos parámetros: el resultado está en caché. (es: cotizar_paquete)

Input Schema

TableJSON Schema

Name	Required	Default
`etapas`	Yes
`mascotas`	No
`meal_plan`	No	BB
`extras_ids`	No
`camino_slug`	No
`presupuesto`	Yes
`habitaciones`	Yes
`nacionalidad`	No
`incluir_mochila`	No
`residente_espana`	No
`categoria_alojamiento`	No	recomendado

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 29, 2026

addedInput schema / properties / camino_slug

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Camino Slug"
+}

AddedAug 26, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses that it auto-selects the best accommodation per night, returns only a single total (never per-night/per-extra prices), falls back to alternative categories when a night has no availability, cites latency of 20-45s, and gives a retry/caching strategy on timeout. This is rich behavioral context annotations alone could not convey.

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?

Dense and front-loaded with the all-in-package purpose and the critical required presupuesto first. However it runs long and the closing Spanish block largely restates the English content, adding redundancy that a slightly tighter form could avoid.

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 an 11-parameter tool with live availability, caching, and extras cross-references, the description covers the important call-time behaviors (timeout retry, availability fallback, required nationality for insurance). With an output schema present and annotations covering the safety profile, nothing essential to invoking it correctly is missing.

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?

With 0% schema description coverage the description carries the load and does so well, enumerating the presupuesto enum values (sin_preferencia | lt_500 | 500_1000 | 1000_1500 | gt_1500), meal_plan codes (RO|BB|HB|FB), categoria_alojamiento options, extras_ids sourcing, mochila pricing, and the nacionalidad/residente_espana insurance dependency. It leaves `etapas` and `habitaciones` structure unexplained in prose, so not a full 5.

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?

States a specific verb and resource: "Quote a complete Camino de Santiago trip as ONE all-in package price," and adds that it is the source of the official Ourway price and returns a single total_paquete_eur. This clearly separates it from siblings like plan_camino_itinerary (planning) and adjust_camino_package (alteration).

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?

Gives explicit triggers ("whenever the user asks how much a Camino costs, wants a quote, or approves an itinerary from plan_camino_itinerary"), naming one sibling as the upstream source. It lacks explicit when-not guidance or mention of adjust_camino_package as the alternative for later changes, so it stops short of a full 5.

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

All Ourway – Camino de Santiago 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.