Hit The Road Rentals
Server Details
Search motorhomes, RVs and campervans worldwide. Get instant results from 300+ rental companies across AU, NZ, US, CA, UK and more. No auth required.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.3/5 across 2 of 2 tools scored.
Both tools have clearly distinct purposes: list_locations returns valid city names, and search_campervans searches for rentals. There is no overlap.
Both tools follow a consistent snake_case verb_noun pattern: list_locations and search_campervans.
With only 2 tools, the server is quite minimal. While it covers the basic search workflow, it lacks additional tools like retrieving results or managing bookings, making it borderline for its domain.
The server only covers the initial search step. After search, there is no tool to retrieve results or book, relying on the user to interact with a web page. This creates a significant gap for automated workflows.
Available Tools
2 toolslist_locationsARead-onlyInspect
List all searchable pickup cities by country. Call this to find valid city names before searching.
| Name | Required | Description | Default |
|---|---|---|---|
| country | No | Country code filter (e.g. AU, NZ, US). Omit to return all supported countries. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false. The description adds context about listing cities but no new behavioral traits beyond 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?
Single sentence with a brief usage instruction. Extremely concise and front-loaded with the key action.
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 simple list tool with one optional parameter and existing annotations, the description is complete. Tells the agent what it does and when to use it.
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 the parameter is fully documented. Description mentions filtering by country but doesn't add meaning beyond schema.
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 clearly states the tool lists searchable pickup cities, with optional country filter. It distinguishes from the sibling tool 'search_campervans' by focusing on location data.
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?
Explicitly advises to call this before searching, implying use case for validating city names. Lacks explicit when-not-to-use or alternative mentions, but context with sibling tool provides clarity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_campervansARead-onlyInspect
Search campervan and motorhome rentals. Returns a URL that pre-fills the search form with your trip details. Click Search on the page to see live results with pricing, availability, and booking options from 160+ rental companies.
| Name | Required | Description | Default |
|---|---|---|---|
| city | Yes | Pickup city name, e.g. "Sydney", "Auckland", "Los Angeles". Required. | |
| country | Yes | Country code: AU, NZ, US, CA, GB, DE, FR, IT, ES, NL. Required. | |
| pickup_date | Yes | Pickup date YYYY-MM-DD. Required. | |
| dropoff_city | No | Return city if different from pickup (one-way). Optional. | |
| dropoff_date | Yes | Return date YYYY-MM-DD. Required. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate readOnlyHint=true and destructiveHint=false. The description adds value by explaining the indirect result mechanism (URL pre-fill), the need for manual clicking, and the scope of 160+ rental companies. No contradictions with 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?
The description is two concise sentences, front-loaded with the main action and result, with no wasted words. Every sentence earns its place.
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?
Given no output schema, the description adequately explains the return value (a URL) and the process. It covers the key behavioral details needed for an agent to correctly invoke and interpret results.
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?
The input schema covers all 5 parameters with descriptions (100% coverage). The description does not add any additional parameter meaning beyond what the schema already provides. Baseline score of 3 is appropriate.
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 clearly states the tool's purpose: searching campervan and motorhome rentals and returning a URL that pre-fills a search form. It distinguishes itself from the sibling tool 'list_locations' by its specific action and outcome.
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?
The description provides context on usage: it returns a URL that requires clicking 'Search' on the page to see live results. It implies the tool is for research rather than direct booking, but does not explicitly exclude alternatives or provide when-not guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!