Skip to main content
Glama

Search relocation deals

search_deals
Read-onlyIdempotent

Search current one-way campervan relocation deals in Europe from Roadsurfer, IndyCampers and Imoova. Filter by pickup city, drop-off city, travel window and provider; every filter is optional. A city matches every pickup or drop-off city within 60 km of it, and must be a name list_cities returns. A deal matches the travel window when its own window overlaps it. Results are sorted by start date and capped by limit; total is the full match count. Each deal has the provider's booking link and a link that opens the map on its pickup city, and the answer has map_url, which opens the map on the searched pickup city, or else the drop-off city, for the requested dates. Read-only: it does not book anything or create alerts. E-mail alerts for new deals are set up on the website. Data comes from the providers a few times a day, so a deal may be gone when the link is opened.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoDrop-off city, for example "Barcelona". Matches drop-off cities within 60 km. Leave out for any drop-off city.
fromNoPickup city, for example "Amsterdam". Matches pickup cities within 60 km. Leave out for any pickup city.
limitNoMost deals to return, 1 to 100. Default 25.
end_dateNoLast day of the travel window, YYYY-MM-DD. Keeps deals whose own window starts on or before it.
providersNoOnly these providers: roadsurfer (Roadsurfer), indiecampers (IndyCampers), imoova (Imoova). Leave out for all three.
start_dateNoFirst day of the travel window, YYYY-MM-DD. Keeps deals whose own window ends on or after it.

Output Schema

NameRequiredDescriptionDefault
noteNoPresent when no deal matches.
dealsYes
totalYesDeals matching the filters.
map_urlYesCamper Rally Map opened on the searched pickup city, or else the drop-off city, for the requested dates.
returnedYesDeals in this answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / map_url
      Added value: +{
      +  "description": "Camper Rally Map opened on the searched pickup city, or else the drop-off city, for the requested dates.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / note
      Added value: +{
      +  "description": "Present when no deal matches.",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "total",
      -  "returned",
      -  "deals"
      -]New value: +[
      +  "total",
      +  "returned",
      +  "deals",
      +  "map_url"
      +]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent and closed-world, and the description adds substantial behavior: 60 km proximity matching for cities, window-overlap matching semantics, sort order by start date, limit capping with total being the full match count, per-deal booking and map links, answer-level map_url fallback logic, and data staleness (deals may vanish before the link is opened).

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?

Front-loaded with purpose, then filters, then matching rules, then output/link behavior, then caveats. Every sentence carries operational information, and there is no filler or restatement of the title.

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 six-parameter, all-optional search tool with an output schema, the description covers matching semantics, result ordering and capping, link contents, and data freshness. An agent has everything needed to call it correctly and to interpret the response without further inference.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds cross-parameter meaning the schema does not convey: that from/to are proximity-matched city names validated by list_cities, and that date filters combine as an overlap test on the deal's own window rather than a containment test.

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 (search one-way campervan relocation deals), names the three providers, and scopes to Europe. It also distinguishes itself from the only sibling by requiring cities come from list_cities, so an agent knows the relationship between the two tools.

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?

Explicitly says every filter is optional and states what the tool does not do (no booking, no alert creation, alerts live on the website), which steers the agent away from misusing it. It lacks an explicit 'use this when' sentence and does not discuss alternatives beyond the list_cities dependency.

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