Skip to main content
Glama

OctoTrip Rental Cars

by app.octotrip

search

Read-onlyIdempotent

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ageNoDriver age. Defaults to 30. Younger drivers may incur surcharges.
currencyNoPreferred ISO 4217 currency code for prices, such as EUR, USD, or GBP. Defaults to EUR.EUR
languageNoPreferred response language code, such as en or de. Defaults to en.en
locationYesPickup location, such as a city, airport, station, address, or landmark.
pickup_dateYesPickup date. Accepts common date formats such as YYYY-MM-DD, DD.MM.YYYY, or natural-language dates.
pickup_timeNoPickup time in 24-hour HH:MM format. Defaults to 12:00.12:00
dropoff_dateYesDropoff date. Must be after the pickup date.
dropoff_timeNoDropoff time in 24-hour HH:MM format. Defaults to 12:00.12:00
dropoff_locationNoOptional different dropoff location. If omitted, the pickup location is used.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already indicate readOnly, idempotent, and non-destructive. The description adds valuable context: real-time external API queries, price-ranked results by SIPP/category, affiliate links, and explicitly states it does not book or store data. No contradiction 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (3 sentences) and well-structured: function, usage guideline, behavioral details. No redundant information.

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?

Given the number of parameters and the presence of an output schema, the description covers purpose, usage, behavior, and limitations adequately. The agent can confidently decide to invoke this tool for car rental searches.

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. The description summarizes optional parameters (dropoff, times, age, currency, language) adding context beyond the schema, though not deeply. A score of 4 reflects this added value.

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?

The description clearly states the tool searches live rental-car offers, specifying the key parameters (pickup location, rental period) and explicit exclusions (flights, hotels, etc.). It distinguishes its purpose effectively.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit instructions on when to use (comparing rental cars) and when not to use (flights, hotels, general travel without car-rental intent). This is exemplary guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All OctoTrip Rental Cars toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined.

Naming Consistency5/5

With a single tool, there is no inconsistency in naming conventions. The name 'search' is a clear verb.

Tool Count2/5

A single tool for a rental car service is too few; users would expect booking, modification, or cancellation capabilities beyond just searching.

Completeness2/5

The server only offers search functionality, lacking essential operations like booking, cancellation, or reservation management, which are significant gaps for the car rental domain.

Resources