Skip to main content
Glama

List my bookings

list_my_bookings
Read-onlyIdempotent

List the signed-in client's bookings with every guide.

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": "list_my_bookings"
  }
}

Input Schema

NameRequiredDescriptionDefault
whenNo
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's remaining job is to disclose scope, which it does by stating results are limited to the signed-in client's bookings across all guides. It says nothing about default ordering, default 'when' value, or how pagination behaves.

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?

A single front-loaded sentence with no filler; the scope constraint comes first. It is not padded, though its brevity leaves the parameters unaddressed.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with three parameters, one enum, zero schema descriptions, and no output schema, the description is too thin: an agent cannot learn the default time window, maximum page size, or expected return contents from it. Only the annotations and the parameter names carry the rest.

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

Parameters2/5

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

Schema description coverage is 0%, so all three parameters (when with its enum, limit capped at 50, offset) are undocumented in both schema and description. The phrase 'with every guide' hints that no guide filter exists, but the description never explains what 'when' defaults to, how limit/offset interact, or whether results are ordered.

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 gives a specific verb and resource ('List ... bookings'), scopes it to the 'signed-in client', and notes coverage across 'every guide', which tells an agent this is a personal, unfiltered listing. It does not explicitly contrast with the singular sibling get_my_booking, but the list-vs-get distinction is inferable from the verb.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance: nothing says to prefer get_my_booking for a single booking, or that this is the entry point before cancel_my_booking or request_booking_change. The only implicit signal is that results are scoped to the signed-in client.

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