Skip to main content
Glama

Black Car Service — Bay Area Ride Quotes

Check payment and reservation confirmation

get_booking_status
Read-onlyIdempotent

Read the current total, payment options and confirmation status for the exact private checkout_url returned by book_ride. Does not charge or change the booking. Never infer confirmation from a pending reservation or payment authorization. Keep the checkout URL private.

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": {
      "checkout_url": "<checkout_url>"
    },
    "name": "get_booking_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
checkout_urlYesExact secure checkout_url from book_ride. Treat it as private; never search for or share it publicly.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety floor is set; the description still adds real value by specifying that no charge occurs and by warning that a pending reservation or payment authorization must not be read as confirmation. The privacy constraint on the URL is additional operational context not present in the annotations. Return field meanings ('total', 'payment options') are named but their shape is not described.

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, front-loaded sentences with the resource and result fields first, then constraints. Minor redundancy: 'Keep the checkout URL private' repeats what the parameter schema already states.

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, so the description must convey the return surface, and it does by naming total, payment options and confirmation status. For a one-parameter read-only lookup with full annotation coverage, this is nearly sufficient; only the result format and any not-found/expired behavior are unaddressed.

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 coverage is 100% and the parameter's own description already covers exactness and privacy, so the description mostly restates it. It does add provenance ('returned by book_ride'), which is useful for constructing the value correctly, but no format or failure-mode guidance beyond that. Baseline 3 is appropriate.

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 (read) and a concrete set of returned facts (current total, payment options, confirmation status) tied to a specific resource (the checkout_url from book_ride). The provenance 'returned by book_ride' and the disclaimer 'does not charge or change the booking' cleanly separate it from book_ride and complete_booking.

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?

Clearly establishes the trigger condition (use the exact URL produced by book_ride) and an explicit negative condition (this is not the tool that charges or modifies a booking). It also warns against inferring confirmation from pending states, which guides interpretation. It stops short of naming complete_booking as the alternative for actually finishing payment, so not a full 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