Skip to main content
Glama
Sign In

Platinumride

by com.platinumride
OverviewDiscussionsAdmin

Send a booking inquiry

create_inquiry

Sends a booking request to the Platinumride team. Use it only after the customer has chosen a route and agreed to the Terms of Service (https://platinumride.com/terms). Do not use it for browsing or quotes; use search_routes and get_route_details for that. Each call sends a new inquiry and is not idempotent, so never call it twice for the same request. Limit: 3 inquiries per connection every 10 minutes. Returns an inquiry reference and a WhatsApp follow-up link to share with the customer. This is not a confirmed booking: the team confirms availability and the final price.

Input Schema

NameRequiredDescriptionDefault
dateYesRequired. Travel date as YYYY-MM-DD, e.g. '2026-12-20'. Must be today or later in UAE time.
timeNoOptional. Preferred local pickup time in 24-hour HH:MM, e.g. '07:30'.
notesNoOptional. Free text for the team: children and child seats, extra stops, special luggage, return trip or other requests.
luggageNoOptional. Number of large suitcases, 0 to 30. Helps the team pick a vehicle.
languageNoOptional. Follow-up language: 'en' (English, default) or 'ar' (Arabic).
routeSlugYesRequired. Exact route slug from search_routes or get_route_details, e.g. 'dubai-to-riyadh-private-transfer'.
passengersYesRequired. Total passengers including children, 1 to 7.
vehicleTierNoOptional. Tier name from the route's price tiers, e.g. 'Premium SUV'. Case-insensitive. Omit if the customer has not chosen.
customerNameYesRequired. Customer's full name, one line.
agreedToTermsYesRequired. true only if the customer has read and agreed to the Terms of Service at https://platinumride.com/terms. The inquiry is rejected otherwise.
customerEmailNoCustomer email address. Give this or customerWhatsApp (at least one is required).
pickupAddressNoOptional. Pickup address, hotel or airport. Add the flight number for airport pickups.
dropoffAddressNoOptional. Drop-off address, hotel or airport.
customerWhatsAppNoWhatsApp number with country code in E.164 format, no spaces, e.g. '+971501234567'. Give this or customerEmail (at least one is required).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changed
    • changedInput schema / properties / agreedToTerms / description
      Previous value: -"Whether the customer has read and agreed to the Terms of Service at https://platinumride.com/terms. Must be true."New value: +"Required. true only if the customer has read and agreed to the Terms of Service at https://platinumride.com/terms. The inquiry is rejected otherwise."
    • changedInput schema / properties / customerEmail / description
      Previous value: -"Customer email address. At least one email or WhatsApp number is required."New value: +"Customer email address. Give this or customerWhatsApp (at least one is required)."
    • changedInput schema / properties / customerName / description
      Previous value: -"Customer's full name."New value: +"Required. Customer's full name, one line."
    • changedInput schema / properties / customerWhatsApp / description
      Previous value: -"Customer WhatsApp number in E.164 format, e.g. '+971501234567'. At least one WhatsApp number or email is required."New value: +"WhatsApp number with country code in E.164 format, no spaces, e.g. '+971501234567'. Give this or customerEmail (at least one is required)."
    • changedInput schema / properties / date / description
      Previous value: -"Travel date in YYYY-MM-DD format, today or later in UAE time."New value: +"Required. Travel date as YYYY-MM-DD, e.g. '2026-12-20'. Must be today or later in UAE time."
    • changedInput schema / properties / dropoffAddress / description
      Previous value: -"Drop-off address."New value: +"Optional. Drop-off address, hotel or airport."
    • changedInput schema / properties / language / description
      Previous value: -"Customer's preferred language for follow-up."New value: +"Optional. Follow-up language: 'en' (English, default) or 'ar' (Arabic)."
    • changedInput schema / properties / luggage / description
      Previous value: -"Number of large suitcases."New value: +"Optional. Number of large suitcases, 0 to 30. Helps the team pick a vehicle."
    • changedInput schema / properties / notes / description
      Previous value: -"Additional trip details for the Platinumride team."New value: +"Optional. Free text for the team: children and child seats, extra stops, special luggage, return trip or other requests."
    • changedInput schema / properties / passengers / description
      Previous value: -"Number of passengers, 1 to 7."New value: +"Required. Total passengers including children, 1 to 7."
    • changedInput schema / properties / pickupAddress / description
      Previous value: -"Pickup address, hotel or airport, optionally including a flight number."New value: +"Optional. Pickup address, hotel or airport. Add the flight number for airport pickups."
    • changedInput schema / properties / routeSlug / description
      Previous value: -"Route slug, e.g. 'dubai-to-riyadh-private-transfer'."New value: +"Required. Exact route slug from search_routes or get_route_details, e.g. 'dubai-to-riyadh-private-transfer'."
    • changedInput schema / properties / time / description
      Previous value: -"Preferred pickup time, e.g. '07:30'."New value: +"Optional. Preferred local pickup time in 24-hour HH:MM, e.g. '07:30'."
    • changedInput schema / properties / vehicleTier / description
      Previous value: -"Optional vehicle tier name available on the route, e.g. 'Premium SUV'. Matching is case-insensitive."New value: +"Optional. Tier name from the route's price tiers, e.g. 'Premium SUV'. Case-insensitive. Omit if the customer has not chosen."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and openWorldHint=true, but the description goes well beyond them: it warns that the call is non-idempotent, quantifies the rate limit as 3 per 10 minutes per connection, describes the return payload (inquiry reference plus WhatsApp follow-up link), and clarifies that the inquiry is not a confirmed booking with availability and final price pending.

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 purpose leads, then constraints, then return behavior, then the caveat that it is not a confirmed booking. Every sentence carries distinct information with no repetition of the title or filler.

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?

For a 14-parameter mutation tool with no output schema, the description covers the safety profile, rate limit, idempotency, expected response, and the key business caveat that confirmation is manual. Nothing an agent needs in order to invoke it correctly is missing.

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 every parameter including the required five and the email/WhatsApp alternation is already documented in the schema. The description adds only indirect guidance, that routeSlug should come from search_routes or get_route_details and that terms agreement is a precondition, which is useful but marginal beyond structured fields.

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 up front: "Sends a booking request to the Platinumride team." It also draws a clear boundary against the siblings search_routes and get_route_details, so an agent can distinguish it without opening 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 Guidelines5/5

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

Explicit preconditions are given (customer has chosen a route and agreed to the Terms of Service), explicit exclusions are given (not for browsing or quotes, use search_routes and get_route_details instead), and a hard usage constraint follows (never call twice for the same request, max 3 per 10 minutes).

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

All Platinumride toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources