Skip to main content
Glama

Airsockfly

Search car rentals

search_cars
Read-onlyIdempotent

Search car rentals for a pickup place, date and time. Prices cover the whole rental; the drop-off place defaults to the pickup place.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pickupLocation": "<pickupLocation>",
      "pickupDate": "<pickupDate>",
      "dropoffDate": "<dropoffDate>"
    },
    "name": "search_cars"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of offers to return, from 1 to 30. Default 10.
driverAgeNoAge of the main driver.
pickupDateYesPickup date, YYYY-MM-DD.
pickupTimeNoPickup time, HH:MM local time.
dropoffDateYesDrop-off date, YYYY-MM-DD.
dropoffTimeNoDrop-off time, HH:MM local time.
pickupLocationYesPickup place: city, airport or address.
dropoffLocationNoDrop-off place. Defaults to the pickup place.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety and freshness profile is covered. The description adds one genuinely useful behavioral fact beyond that — that quoted prices cover the whole rental period — while the drop-off default it also states is already documented in the dropoffLocation schema. Nothing is said about currency, availability, or how results are ranked.

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?

Two short sentences, front-loaded with the core action and then the one non-obvious pricing rule. Every clause carries information; nothing is redundant or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an eight-parameter read-only search with full schema coverage and annotations, the definition supplies enough to call it correctly. The remaining gap is return-shape context — no output schema exists and the description does not say what an offer contains or whether results are paged beyond the limit parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with every parameter documented including formats, ranges and the dropoffLocation default, so the schema carries the load. The description adds no format, unit or constraint detail beyond what is already there, which is the expected baseline for full coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ("Search car rentals") and scopes it to a pickup place, date and time, which is enough to separate it from the flight/hotel/insurance siblings by resource alone. It stops short of explicitly naming when a different search tool is the right call.

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

Usage Guidelines3/5

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

Usage is implied by the resource name and the required pickup/date parameters, but there is no explicit when-to-use guidance, no prerequisites, and no statement of when this tool is the wrong choice versus search_flights, search_hotels or search_parking.

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