Skip to main content
Glama

Find a customer's bookings

find_bookings
Read-only

Retrieves upcoming appointments for a specified customer phone number in international format, so agents can check that customer's schedule without accessing other customers' bookings.

Instructions

Upcoming bookings for one phone number. There is no way to list other customers' bookings.

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": {
      "customer_phone": "<customer_phone>"
    },
    "name": "find_bookings"
  }
}

Input Schema

NameRequiredDescriptionDefault
customer_phoneYesCustomer phone in international format, e.g. +355691234567

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a safe read. The description adds genuine value beyond it by scoping results to upcoming bookings only, implying past bookings are excluded and that a phone number is the sole lookup key. It does not say what happens for an unknown phone (empty result vs error) or how results are ordered, which tempers the score.

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 short sentences with zero filler, and the primary purpose is front-loaded before the scope limitation. Slightly clipped to the point of omitting a verb, but nothing is wasted.

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 single-parameter read tool with annotations and no output schema, this covers the essentials: what it returns (upcoming bookings), for whom (one phone number), and what it cannot do. The remaining gap is edge-case behavior for unmatched phone numbers.

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% and includes the international format example, so the schema carries the parameter burden. The description only reinforces that exactly one phone number is required, adding no format or matching-behavior detail beyond what the schema already states.

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?

Names the resource (bookings) with a temporal scope (upcoming) and a keying constraint (one phone number), which is enough to tell it apart from write siblings like create_booking and cancel_booking. It stops short of a clean verb phrasing like 'Retrieve', but the intent is unambiguous.

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?

The statement 'There is no way to list other customers' bookings' functions as an explicit when-not: it tells the agent it must already have a customer's phone number and cannot enumerate customers. No sibling alternative (e.g. find_slots) is named, which keeps it from a 5.

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