Skip to main content
Glama

Côte Privée: private driver in Burgundy

Status of a booking request

get_booking_status
Read-onlyIdempotent

What became of a booking request: requested (no answer yet), confirmed (with the payment link of the full price once it can be paid), declined (with the driver's note), deposit_paid (paid in full) or cancelled, its days and its total. Needs the reference and the e-mail address of the request.

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

Input Schema

NameRequiredDescriptionDefault
refYesCP-XXX-XXX
langNoar: Arabic notes, data in English.
emailYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), and the description adds real value beyond them by disclosing what accompanies each status (payment link for confirmed, driver's note for declined, days and total). It also reveals the identity requirement (ref + email) needed to query.

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?

Two sentences, front-loaded with the status enumeration, and every clause earns its place by describing a distinct outcome. The single long status sentence is slightly dense but not wasteful.

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?

There is no output schema, so the description carries the burden of explaining return values, which it does by listing statuses, the payment link, driver's note, days, and total. Combined with a well-annotated schema for inputs, this is nearly complete.

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 67%, so the schema already documents ref ('CP-XXX-XXX'), email format, and the lang enum with its note. The description only reaffirms that ref and email are needed and belong to the request, adding little new semantic detail; the baseline of 3 fits.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description reads as a lookup of a booking request's state and enumerates every possible status (requested, confirmed, declined, deposit_paid, cancelled), which makes the resource and returned information unambiguous. It does not explicitly name a sibling to distinguish from, but the retrieval nature is clear against request_booking.

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?

It states a prerequisite ('Needs the reference and the e-mail address of the request'), which implies when the tool is callable, but it gives no explicit when-to-use vs. when-not guidance or alternative tools (e.g., request_booking). Usage is implied rather than spelled out.

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