Campings en ruta y dónde dormir en viajes por carretera: guía BuscaTuCamping de España y Europa.
Scored across 2 tools
The two tools have related but distinguishable purposes: one lists campings along a route without scheduling, while the other builds an overnight itinerary with timing and vehicle constraints. The descriptions clarify the intended use cases, though an agent could still hesitate for a vague request like 'campings entre A y B' versus 'dónde dormir entre A y B'.
Both names use Spanish snake_case, which is readable and consistent at the casing level. However, the grammatical patterns differ: 'campings_en_ruta' is a noun phrase while 'planificar_ruta' is a verb phrase, so there is no predictable verb_noun convention across the set.
Two tools is borderline thin for a camping route-planning server, even a narrowly scoped one. Each tool is substantive, but there is little room for complementary operations such as direct campground lookup, filtering, or detail retrieval.
The surface covers two important workflows: discovering campings along a route and planning overnight stops. It lacks more direct discovery operations such as searching by place or name, filtering by services, or retrieving campground details beyond returning an external URL, which may leave agents at a dead end for related camping questions.
Lista los campings que quedan cerca de un trayecto por carretera, en el sentido del viaje, con el km de la ruta en el que caen, el desvío, el estado de temporada en la fecha y la URL de su ficha. Para "qué campings hay entre A y B" sin planificar horarios.
| Name | Required | Description | Default |
|---|---|---|---|
| fecha | No | Fecha del viaje YYYY-MM-DD (por defecto hoy). Decide el estado de temporada de cada camping. | |
| perro | No | Solo campings que admiten perros. | |
| origen | Yes | Nombre de la población o provincia (p. ej. "Burgos", "Asturias"); se reconocen provincias y poblaciones con campings en la guía. Si no se reconoce, coordenadas "lat,lng" del lugar. | |
| destino | Yes | Nombre de la población o provincia (p. ej. "Burgos", "Asturias"); se reconocen provincias y poblaciones con campings en la guía. Si no se reconoce, coordenadas "lat,lng" del lugar. | |
| radio_km | No | Desvío máximo en línea recta desde la carretera, por defecto 25. | |
| vehiculo | No | coche = turismo; camper, autocaravana o caravana = perfil de vehículo grande. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds behavioral value by explaining that results follow the 'sentido del viaje' and include the route-km, detour, season status, and profile URL, which is useful context not present in the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with zero filler, and the primary purpose plus returned fields are front-loaded before the usage cue. Every clause carries information relevant to selecting or invoking the tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With six parameters and no output schema, the description compensates by naming the key return fields (km, desvío, season state, URL). It omits some parameter-level defaults like radio_km, but those are fully covered by the schema, so the definition is nearly complete for this tool's complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so all six parameters are fully documented in the schema. The description only loosely reinforces that 'fecha' drives season status and that results follow the trip direction; it does not add syntax or constraints beyond what the schema already states.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description gives a specific verb ('Lista') and resource ('campings... cerca de un trayecto por carretera'), and enumerates the returned fields (km de la ruta, desvío, estado de temporada, URL). It separates itself from the sibling planificar_ruta by scoping the use case to 'qué campings hay entre A y B' without schedule planning.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It provides an explicit when-to-use phrase ('Para "qué campings hay entre A y B" sin planificar horarios'), which implicitly routes schedule-planning requests to planificar_ruta. It does not name the sibling by name or state when not to use this tool, so it falls short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Planifica dónde dormir en un viaje por carretera. Úsela cuando el usuario pregunte dónde hacer noche, en cuántas etapas hacer un viaje o cómo repartir un trayecto largo en coche, camper, autocaravana o caravana. Calcula la ruta con el perfil del vehículo, la hora a la que conviene parar según la hora de salida, el máximo de conducción, la comida y los descansos, y devuelve 8-12 campings de pernocta alcanzables a esa hora (con desvío real por carretera, hora de llegada y estado de temporada) más un itinerario por noches con alternativas. Cada camping lleva su URL en buscatucamping.com.
| Name | Required | Description | Default |
|---|---|---|---|
| fecha | No | Fecha del viaje YYYY-MM-DD (por defecto hoy). Decide el estado de temporada de cada camping. | |
| perro | No | Solo campings que admiten perros. | |
| max_km | No | Kilómetros máximos por jornada (alternativa a max_conduccion_h). | |
| origen | Yes | Nombre de la población o provincia (p. ej. "Burgos", "Asturias"); se reconocen provincias y poblaciones con campings en la guía. Si no se reconoce, coordenadas "lat,lng" del lugar. | |
| destino | Yes | Nombre de la población o provincia (p. ej. "Burgos", "Asturias"); se reconocen provincias y poblaciones con campings en la guía. Si no se reconoce, coordenadas "lat,lng" del lugar. | |
| radio_km | No | Desvío máximo en línea recta desde la carretera, por defecto 25. | |
| vehiculo | No | coche = turismo; camper, autocaravana o caravana = perfil de vehículo grande. | |
| prioridad | No | Entre trazados alternativos (solo coche): comoda = vías anchas y rápidas (por defecto), rapida = menos tiempo. | |
| comida_min | No | Minutos de parada para comer si se cruzan las 14:00, por defecto 60. | |
| hora_dormir | No | Hora (0-24) a la que se quiere estar en el camping, por defecto 20. | |
| hora_salida | No | HH:MM, por defecto 10:30. | |
| descanso_min | No | Duración de cada descanso, por defecto 15. | |
| velocidad_kmh | No | Velocidad media del viajero como tope tramo a tramo, por defecto 90. | |
| max_conduccion_h | No | Horas máximas al volante por jornada, por defecto 6. Use max_km si prefiere un tope en km. | |
| descanso_cada_min | No | Cada cuántos minutos de conducción se descansa (0 = sin descansos), por defecto 120. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is free to add planning behavior: it discloses how the route is computed (vehicle profile, departure time, max driving, lunch, breaks) and what comes back (real road detour, arrival time, season status, alternatives, per-campsite URL). No auth or rate-limit notes, but nothing contradicts the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Four sentences, front-loaded with purpose then usage triggers, then computation, then return shape. Dense but every sentence carries information; the only mild bloat is the final URL sentence, which is still useful for the agent to know what it gets.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 15-parameter tool with no output schema, the description does the important extra work of describing the return payload (count, fields, itinerary with alternatives). What remains uncovered (error behavior for unrecognized origins) is handled in the schema's parameter descriptions, so the description is close to complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with self-documenting parameters, defaults and enums, so the schema carries the semantics and baseline 3 applies. The description adds a little meaning by framing which inputs drive the calculation (vehicle profile, hora_salida, max driving, comida, descansos), but it does not explain interactions such as max_km vs max_conduccion_h beyond what the schema already states.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Planifica dónde dormir en un viaje por carretera') and enumerates the concrete outputs: 8-12 campsites reachable at a given hour plus a nightly itinerary with alternatives. This is far more specific than the sibling campings_en_ruta, though the sibling is never named explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives explicit trigger conditions with example user phrasings ('dónde hacer noche', 'en cuántas etapas', 'cómo repartir un trayecto largo'), which is strong when-to-use guidance. It stops short of stating when NOT to use it or explicitly routing to campings_en_ruta for simpler lookups.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
campings_en_ruta3 fields changedInput schema / properties / destino / descriptionPrevious value: -"Coordenadas \"lat,lng\" (recomendado) o nombre de una población o provincia con campings."New value: +"Nombre de la población o provincia (p. ej. \"Burgos\", \"Asturias\"); se reconocen provincias y poblaciones con campings en la guía. Si no se reconoce, coordenadas \"lat,lng\" del lugar."Input schema / properties / origen / descriptionPrevious value: -"Coordenadas \"lat,lng\" (recomendado) o nombre de una población o provincia con campings."New value: +"Nombre de la población o provincia (p. ej. \"Burgos\", \"Asturias\"); se reconocen provincias y poblaciones con campings en la guía. Si no se reconoce, coordenadas \"lat,lng\" del lugar."Input schema / properties / perroAdded value: +{
+ "description": "Solo campings que admiten perros.",
+ "type": "boolean"
+}planificar_ruta2 fields changedInput schema / properties / destino / descriptionPrevious value: -"Coordenadas \"lat,lng\" (recomendado) o nombre de una población o provincia con campings."New value: +"Nombre de la población o provincia (p. ej. \"Burgos\", \"Asturias\"); se reconocen provincias y poblaciones con campings en la guía. Si no se reconoce, coordenadas \"lat,lng\" del lugar."Input schema / properties / origen / descriptionPrevious value: -"Coordenadas \"lat,lng\" (recomendado) o nombre de una población o provincia con campings."New value: +"Nombre de la población o provincia (p. ej. \"Burgos\", \"Asturias\"); se reconocen provincias y poblaciones con campings en la guía. Si no se reconoce, coordenadas \"lat,lng\" del lugar."campings_en_rutaplanificar_rutaBusca campings de España y Europa por zona, servicios y fechas, con temporada verificada.
Vanlife & RV data: roadbooks, fuel, tolls, ferries, visas, holidays, hazards, weather. openvan.camp
Search Australian campsites, caravan parks and free camps; weather, gear, road trips and booking.
Search campervans and motorhomes worldwide. 300+ rental companies. AU, NZ, US, CA, UK and more.
Add one secure layer between your agents and this server.