Skip to main content
Glama

PRIVYDE Private Chauffeur

Build a pre-filled booking link from known trip details for the user to review and submit

get_booking_link
Read-onlyIdempotent

Build a pre-filled booking link from known trip details for the user to review and submit. Returns a URL only: it does NOT submit a booking. The booking is a request confirmed by a human afterwards. The pickup must respect the minimum notice (Madrid time, longer at night, and it depends on the vehicle category; https://privyde.com/developers#lead-time), which the booking form checks.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_booking_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoPickup date, YYYY-MM-DD.
langNoLanguage for names and URLs. Defaults to "es".
nameNo
timeNoPickup time, 24h HH:MM.
emailNo
phoneNo
originNoPickup location (address, airport, hotel).
luggageNo
passengersNo
destinationNoDrop-off location.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this by spelling out that no booking is created and a human confirms afterwards — valuable clarity about the side-effect boundary. It also surfaces a non-obvious business constraint (minimum pickup notice, Madrid time, night and vehicle-category dependent) with a doc URL, and notes the booking form enforces it. It stops short of saying what happens if the notice is violated (rejected link? form error?).

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?

Four short sentences, front-loaded with the core action and the 'URL only' caveat, then the human-confirmation model, then the constraint. Every sentence carries information; the parenthetical about night hours and vehicle category is dense but necessary for correctness.

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 a 10-parameter tool with no output schema, the description does the important work of defining the return value ('a URL only') and the human-in-the-loop contract. What is missing is field-level guidance for the five undocumented parameters and any statement of failure behavior when the lead-time rule is not met.

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

Parameters2/5

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

Schema coverage is only 50%, and the description compensates for almost none of the gap: name, email, phone, luggage, and passengers have no descriptions in either place, and there are zero required parameters, so an agent gets no signal about which fields are needed to produce a usable link. The only semantic added is the minimum-notice rule, which implicitly constrains date/time but does not explain format or resolution.

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 ('Build a pre-filled booking link') plus its input basis ('known trip details'), and immediately negates the most likely misreading: 'Returns a URL only: it does NOT submit a booking.' An agent can tell this apart from a quote or submit tool without inspecting any 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 intended flow is clearly implied: gather trip details, build the link, hand it to the user who reviews and submits, with human confirmation afterwards. However, no sibling is named and there is no explicit 'use get_quote instead when...' routing, so the agent must infer the boundary against the quote tool from names alone.

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