Skip to main content
Glama

Airsockfly

List bookings

list_bookings
Read-onlyIdempotent

List the user's orders, newest first, with status and 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": "list_bookings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of items to return.
statusNoShow only orders with this status.

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, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: results are sorted newest first and include status and totals. It says nothing about default page size, pagination beyond the limit cap, or result volume.

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 sort order and returned fields are packed into one clause. The only cost is the slight vocabulary drift from 'bookings' to 'orders'.

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 simple read-only list tool with two optional, fully documented parameters and no output schema, the definition covers purpose, ordering, and returned fields adequately. Minor gaps are the default limit and any paging behavior, which the annotations do not supply either.

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%, with both the limit and status parameters documented in the schema, so the baseline is 3. The description adds no extra meaning about the parameters themselves — it only previews what returned records contain.

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 ('List the user's orders') plus the ordering ('newest first') and returned fields ('status and totals'), so an agent knows exactly what it gets. It does not differentiate itself from siblings such as get_booking or the search_* tools, and it swaps the tool's 'bookings' vocabulary for 'orders', which could briefly confuse matching.

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 only implied: 'the user's orders' scopes it to the caller's own records, which distinguishes it from global search tools. There is no explicit statement of when to prefer it over get_booking (single record) or search_flights, and no exclusions or alternatives are named.

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