Skip to main content
Glama

any.cab

Price a transfer

get_quote
Read-only

Fixed price for a private transfer between two places in Malta, for every vehicle that fits the group. Returns one offer per vehicle with price, max_pax, luggage, a price breakdown and a quote_id valid for 15 minutes.

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": {
      "from": "<from>",
      "to": "<to>",
      "pickup_at": "<pickup_at>",
      "pax": "<pax>"
    },
    "name": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesEither the string "MLA" (Malta International Airport) or a place object from search_locations, passed as is.
paxYesNumber of passengers
fromYesEither the string "MLA" (Malta International Airport) or a place object from search_locations, passed as is.
pickup_atYesPickup time, Malta local, e.g. "2026-11-25T10:00" (or ISO 8601 with offset). At least 60 minutes ahead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, non-idempotent and open-world behavior, so the description is not required to restate safety. It adds genuinely useful context beyond that: one offer per fitting vehicle, a price breakdown, and a quote_id that expires in 15 minutes — a constraint that directly affects follow-up booking behavior.

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 dense sentences with zero waste: the first establishes what is priced and for whom, the second enumerates the return payload and the expiry constraint. Front-loaded and easy to scan.

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?

With no output schema, the description carries the return-shape burden and does so well (per-vehicle offers, price, max_pax, luggage, breakdown, quote_id). It is nearly complete for a read-only pricing tool; only edge behavior such as what happens when no vehicle fits the group is unstated.

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%, so the schema already documents from/to, pickup_at and pax fully. The description adds only the framing that offers are generated per vehicle fitting the group, which marginally clarifies pax, but no format or edge-case detail beyond the schema.

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?

States a specific verb and resource — fixed-price quoting for a private transfer between two Malta places — and clarifies the scope is every vehicle fitting the group. An agent can tell this is a pricing/quote tool rather than a booking or location-search tool without opening the schema.

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?

The use case is implied (get a price before booking) and the 15-minute quote validity gives a useful timing constraint, but there is no explicit when-to-use/when-not statement nor any named alternative such as get_rates or create_booking.

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