Skip to main content
Glama

Black Car Service — Bay Area Ride Quotes

Estimate a Bay Area SUV fare

quote_ride

Estimate Black Car Service SUV fares in the San Francisco Bay Area for SFO, OAK and SJC airport transfers, point-to-point rides and hourly chauffeur service, for 1–6 passengers. Pickup and destination must both resolve to California or Nevada, and at least one endpoint must be in the nine-county San Francisco Bay Area; geographic eligibility does not guarantee service. Pickup dates begin tomorrow in America/Los_Angeles. Hourly rides require hours (1–24); other ride types omit hours. The price excludes extras and gratuity. No availability check, hold, reservation, or payment is performed.

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": {
      "trip_type": "<trip_type>",
      "pickup_address": "<pickup_address>",
      "dropoff_address": "<dropoff_address>",
      "pickup_at": "<pickup_at>",
      "passengers": "<passengers>"
    },
    "name": "quote_ride"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursNoRequired for hourly service; omit for airport and one-way rides. Billed minimums apply.
pickup_atYesISO 8601 timestamp with explicit UTC offset. Clarify the customer's pickup time in America/Los_Angeles; account for daylight saving time.
trip_typeYes
passengersYes
pickup_addressYesFull pickup street address or airport, including city and state.
dropoff_addressYesFull destination. For hourly service returning to pickup, repeat the pickup address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / pickup_at / pattern
      Previous value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
  2. Changed1 schema field changed
    • changedInput schema / properties / passengers / maximum
      Previous value: -7New value: +6
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial behavioral context beyond the annotations: the quote excludes extras and gratuity, geographic eligibility does not guarantee service, dates begin tomorrow in America/Los_Angeles, and no hold or payment is created. This is exactly the sort of side-effect and scope disclosure annotations alone (readOnlyHint=false, openWorldHint=true) cannot convey.

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?

Purpose is front-loaded in the first sentence and every subsequent clause carries a real constraint. The middle sentence packs geography, eligibility caveat, and the date rule into one long run-on, which costs a little readability but no filler is present.

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

Completeness3/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 burden of describing what comes back, but it only says the price excludes extras and gratuity. It never states the response shape (fare amount, currency, itemization, quote validity/expiry), which is a meaningful gap for an estimation tool.

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?

Goes well beyond the 67%-covered schema: it explains which endpoints must resolve to CA/NV and the Bay Area (applying to pickup_address and dropoff_address), the 1–6 passenger ceiling, the tomorrow-start date rule with timezone, and the conditional rule that hours applies only to hourly trips. These are business rules the schema cannot express.

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?

A specific verb ("Estimate") plus a specific resource ("Black Car Service SUV fares") scoped to a region and a set of ride types. The closing sentence ("No availability check, hold, reservation, or payment is performed") cleanly separates it from book_ride and check_ride_availability without needing to name them.

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

Usage Guidelines4/5

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

It states the eligibility conditions for using the tool (CA/NV endpoints, at least one in the nine-county Bay Area, pickup from tomorrow) and, crucially, what it does NOT do (no availability check, hold, reservation, or payment), which implicitly routes the agent to check_ride_availability or book_ride. It stops short of naming those siblings as alternatives, so it falls short of a 5.

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