OctoTrip Rental Cars
Server Details
Free, no-login rental car search with real-time pricing. Affiliate-attributed booking links.
- 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.2/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of confusion between tools. The single 'search' tool has a clearly distinct purpose.
There is only one tool, so naming consistency is not an issue. The verb 'search' is appropriate for the tool's function.
A single tool for a rental car service is too few. The server likely needs additional tools for booking, cancellation, or management to be useful for agents.
The tool surface is severely incomplete. It only provides search functionality, with no ability to complete bookings, manage reservations, or handle other essential operations for a rental car service.
Available Tools
1 toolsearchAInspect
Search for rental cars by location, dates, and preferences. Returns available cars from multiple vendors grouped by category (economy, compact, SUV, etc.), showing the cheapest options in each. Booking links contain affiliate attribution. Dates can be in any common format (YYYY-MM-DD, DD.MM.YYYY, 'August 1, 2026', etc.). Driver age defaults to 30 if not specified — younger drivers may incur surcharges.
| Name | Required | Description | Default |
|---|---|---|---|
| age | No | ||
| currency | No | EUR | |
| language | No | en | |
| location | Yes | ||
| pickup_date | Yes | ||
| pickup_time | No | 12:00 | |
| dropoff_date | Yes | ||
| dropoff_time | No | 12:00 | |
| dropoff_location | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It discloses affiliate attribution, date format flexibility, driver age default and surcharges. It does not cover edge cases like invalid location or empty results, but overall it is fairly transparent for a search tool.
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 three concise sentences, front-loaded with the main purpose and output format. Every sentence adds value without waste. It efficiently conveys key 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 complexity (9 parameters, 3 required, output schema exists), the description covers the essential purpose, output grouping, and behavioral notes. It misses details on some parameters but is still reasonably complete for a search tool.
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 0%, so the description must compensate. It explains the meaning of age (default and surcharge) and date formats, but does not describe other parameters like currency, language, times, or dropoff_location. It adds some value but leaves many parameters undocumented.
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 for rental cars by location, dates, and preferences, specifying the resource and action. It also describes the output structure (grouped by category, cheapest options), which distinguishes it well even without sibling tools.
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 when to use (searching rental cars) and includes important notes like affiliate attribution and age defaults. However, it lacks explicit guidance on when not to use this tool or alternatives, but since no siblings exist, this is acceptable.
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!