Skip to main content
Glama

PRIVYDE Private Chauffeur

Price a transfer, an hourly/daily disposal or a long-distance trip from the published rate card, read-only, exactly like POST /api/v1/quote: per real road kilometre, closed at booking

get_quote
Read-onlyIdempotent

Price a transfer, an hourly/daily disposal or a long-distance trip from the published rate card, read-only, exactly like POST /api/v1/quote: per real road kilometre, closed at booking. Never an estimate: when the trip cannot be measured or needs a human, the answer says so (quotable: false, requiresHumanValidation, reasonCode) instead of inventing a price. Returns the fare for the requested tier and, when quotable, the other tier's total too. Not saved (persisted: false, no quoteId): to actually request the service, call POST /api/v1/booking or build a link with get_booking_link. The pickup must respect the minimum notice (longer at night, and it depends on the vehicle category; https://privyde.com/developers#lead-time).

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": {
      "serviceType": "<serviceType>",
      "tier": "<tier>",
      "origin": "<origin>",
      "date": "<date>",
      "time": "<time>",
      "passengers": "<passengers>"
    },
    "name": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesPickup date, YYYY-MM-DD, Madrid calendar date.
langNoLanguage for names and URLs. Defaults to "es".
tierYesVehicle class to price.
timeYesPickup time, 24h HH:MM, Madrid wall-clock time.
addonsNo
originYesPickup location (address, airport, hotel).
passengersYes
destinationNoDrop-off location. Required unless serviceType is SRV_DISPOSITION.
serviceTypeYesSRV_TRANSFER = point to point with one end in the Madrid region; SRV_DISPOSITION = chauffeur at disposal by the hour or by the day; SRV_LONG_DISTANCE = intercity, in either direction.
durationDaysNoDays at disposal (SRV_DISPOSITION, from 2 days).
durationHoursNoHours at disposal (SRV_DISPOSITION).
originLocalityNoTown of the pickup, when known (keeps a province from being mistaken for a city).
dispositionAreaNoMain area or destination of an "at disposal" service. Required for SRV_DISPOSITION once card-on-file is enabled (currently off); informational, never priced.
oneWayOrRoundTripNo
destinationLocalityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld=false/idempotent/non-destructive, and the description adds substantial context on top: results are non-persisted with no quoteId, failure is expressed as quotable:false plus requiresHumanValidation and reasonCode, both tier totals are returned, and pricing is closed at booking. It also discloses a non-obvious constraint (lead time varies at night and by vehicle category, with a doc link).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Front-loaded with purpose, then consequences, then the alternative path — a sensible order. The prose is dense and semicolon-chained with parenthetical error-field lists, which is slightly heavy, but every sentence carries information rather than filler.

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?

No output schema exists, and the description compensates by naming the key return fields (quotable, requiresHumanValidation, reasonCode, other-tier total, persisted). Given 15 parameters, a few (addons, oneWayOrRoundTrip, locality fields) are left entirely to the schema, but the critical behavioral and failure semantics are all present.

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

Parameters5/5

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

With 73% schema coverage the schema already describes most fields, but the description adds meaning the schema does not: 'tier' controls not only the requested fare but which other tier's total is echoed back, and lead-time depends on vehicle category and time of day. Per-km basis ('per real road kilometre') clarifies how fare is computed.

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?

Opens with a concrete verb (price) and enumerates the exact resource set (transfer, hourly/daily disposal, long-distance trip), plus the parity claim 'exactly like POST /api/v1/quote'. An agent can tell instantly this is the pricing tool rather than a booking or catalog tool.

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?

Explicitly separates pricing from booking: 'Not saved (persisted: false, no quoteId)' and routes to POST /api/v1/booking or the sibling get_booking_link for an actual request. It also states a precondition (pickup must respect the minimum notice) and states what the tool will NOT do (never invent a price), which is exactly the when/when-not guidance needed.

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