Skip to main content
Glama

Search bookings

search_bookings
Read-only

Search bookings by activity, client, status, or start date. Returns booking summaries with participants and payment totals.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_bookings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoActivity or client name to match.
offsetNo
statusNo
to_dateNo
from_dateNo
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine value by disclosing the return shape (booking summaries with participants and payment totals), but says nothing about pagination or result limits even though limit/offset exist, and nothing about ordering or empty-result behavior.

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 tight, front-loaded sentences with no filler: the first covers inputs, the second covers outputs. Nothing is wasted, though the wording is compact enough that a couple of filter/range details are squeezed out rather than clarified.

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?

For a 7-parameter search tool with no output schema, the definition covers purpose and return content but leaves pagination semantics, date-range behavior (from_date vs to_date), and the business_id scoping rule to the schema alone. Adequate to call correctly, but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 29% across 7 parameters, so the description must compensate; it does partially by naming the four filtering concepts (activity or client name, status, start date). It leaves limit, offset, to_date and business_id unexplained, and 'start date' is ambiguous about whether from_date/to_date form a range.

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?

States a specific verb and resource (search bookings) plus the filter dimensions available (activity, client, status, start date) and what comes back (summaries with participants and payment totals). It is clearly distinguishable from get_booking by being a filtered list, though it never names a sibling explicitly.

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?

Usage is implied by the search framing and the enumerated filters, but there is no explicit guidance on when to use this versus get_booking, get_attention_bookings, or the cancel/complete booking tools, and no exclusions or prerequisites are stated.

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