OctoTrip Rental Cars
Server Details
Free, no-login rental car search with real-time pricing.
- 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.9/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined.
With a single tool, there is no inconsistency in naming conventions. The name 'search' is a clear verb.
A single tool for a rental car service is too few; users would expect booking, modification, or cancellation capabilities beyond just searching.
The server only offers search functionality, lacking essential operations like booking, cancellation, or reservation management, which are significant gaps for the car rental domain.
Available Tools
1 toolsearchARead-onlyIdempotentInspect
Searches live rental-car offers for a pickup location and rental period, optionally with a different dropoff location, pickup/dropoff times, driver age, currency, and language. Use this when the user wants to compare available rental cars, prices, vendors, categories, or booking links for a specific trip. Do not use it for flights, hotels, public transport, or general travel planning unless the user has car-rental intent. The tool queries external provider APIs in real time, returns price-ranked results grouped by SIPP/category, and may include affiliate booking links. It does not book cars, modify reservations, charge users, or store user data.
| Name | Required | Description | Default |
|---|---|---|---|
| age | No | Driver age. Defaults to 30. Younger drivers may incur surcharges. | |
| currency | No | Preferred ISO 4217 currency code for prices, such as EUR, USD, or GBP. Defaults to EUR. | EUR |
| language | No | Preferred response language code, such as en or de. Defaults to en. | en |
| location | Yes | Pickup location, such as a city, airport, station, address, or landmark. | |
| pickup_date | Yes | Pickup date. Accepts common date formats such as YYYY-MM-DD, DD.MM.YYYY, or natural-language dates. | |
| pickup_time | No | Pickup time in 24-hour HH:MM format. Defaults to 12:00. | 12:00 |
| dropoff_date | Yes | Dropoff date. Must be after the pickup date. | |
| dropoff_time | No | Dropoff time in 24-hour HH:MM format. Defaults to 12:00. | 12:00 |
| dropoff_location | No | Optional different dropoff location. If omitted, the pickup location is used. |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description adds context beyond annotations: queries external APIs in real time, returns price-ranked results grouped by SIPP/category, may include affiliate links. No contradiction with annotations (readOnly, idempotent, non-destructive).
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 efficiently convey purpose, usage, behavior, and limitations. Front-loaded with key action, no redundant or irrelevant information.
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 the presence of an output schema, the description need not explain return values. It covers all necessary aspects: what the tool does, when to use, behavioral traits, parameter context, and what it does not do. Sufficient for an agent to select and invoke correctly.
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 schema has 100% description coverage, so baseline is 3. However, the description adds extra context like natural-language date acceptance, default times, and age surcharge hints, providing meaningful additional guidance.
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 searches live rental-car offers for a given location and rental period, with optional parameters. It distinguishes from other travel services (flights, hotels) and covers specific capabilities like comparing prices, vendors, and booking links.
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 states when to use ('user wants to compare available rental cars') and when not to use ('do not use it for flights, hotels...'). Also clarifies tool does not book, modify, charge, or store data, which prevents misuse.
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!