Skip to main content
Glama

podyx_v1_list_bookings

Read-onlyIdempotent

Retrieve active session-purchase bookings with pagination and filters for status, client, or user; read-only preview excludes calendar and blocker-only records.

Instructions

listBookings GET /api/v1/bookings. Active session purchases, excluding calendar records and manual blocker-only records. Blocking slots are omitted from mixed purchases. Original payment status describes only the first linked payment, not later add-on charges. Money may be null for historical/unpriced records and otherwise uses the booking currency precision. Read/preview only. Follow all pagination; a quote does not reserve a slot or lock a price.

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

Input Schema

NameRequiredDescriptionDefault
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.3/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), and the description goes well beyond them: exclusion of calendar and blocker-only records, omission of blocking slots from mixed purchases, the fact that original payment status reflects only the first linked payment, and null/unprecise money semantics. What is missing is any statement about result ordering or how pagination termination is signalled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Correctly front-loads identity and scope in the first two clauses, and the domain caveats are dense but earn their place. The trailing quote/reservation sentence is irrelevant to a list endpoint and dilutes an otherwise tight block.

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 paginated list tool with a nested params object, no output schema, and effectively zero parameter documentation, the description covers result-set semantics and money/payment caveats well. It leaves open what fields records contain and how to drive pagination, which an agent must infer.

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?

The description says nothing about the parameters — no explanation of allowed status values, the client_id vs user_id precedence, or page/per_page behavior. Schema coverage is reported as 0%, so the burden falls entirely on the description and it does not compensate; only two nested params carry inline schema text.

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 ("listBookings GET /api/v1/bookings") and narrows scope precisely: "Active session purchases, excluding calendar records and manual blocker-only records." That scope statement distinguishes it from podyx_v1_get_booking and the reports tools, 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?

"Read/preview only" and "Follow all pagination" give operational guidance, but there is no articulation of when to call this versus podyx_v1_get_booking, podyx_v1_list_sessions, or the report tools. The closing clause about quotes not reserving a slot appears to be boilerplate from quote tooling and does not guide usage of a listing call.

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

Deploy Server

Other Tools