Skip to main content
Glama

Aurinia — book across venues via your AI assistant

list_current_bookings

Read-only

The user's current/upcoming bookings at a network venue (by date, nearest first). Each has a status field (e.g. booked/confirmed/cancelled) — distinguish active vs cancelled. provider_id optional (without it — the first venue). Requires authorization.

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_current_bookings"
  }
}

Input Schema

NameRequiredDescriptionDefault
provider_idNoVenue id from find_providers. Omit to use the first venue in the network.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / provider_id / description
      Added value: +"Venue id from find_providers. Omit to use the first venue in the network."
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds genuinely new behavioral context: results are date-ordered nearest-first, each record carries a status field spanning booked/confirmed/cancelled, and authorization is required. That last point is important operational information absent from the annotations. It does not mention result limits or pagination, which keeps it below a 5.

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 sentences, front-loaded with the resource and scope, then the parameter caveat. The nested parentheticals make it slightly dense to parse, but no sentence 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 one-parameter, no-output-schema read tool, the description covers the important unknowns: ordering, the presence and meaning of the status field, and the authorization requirement. Only result-count/pagination behavior is left unspecified, which is a minor gap.

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 coverage is 100% and the schema already documents provider_id including the omit-to-use-first-venue default. The description restates that default, which mildly reinforces the behavior but adds no new syntax or semantics. Baseline 3 is appropriate when the schema carries the parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('current/upcoming bookings at a network venue') and scopes it temporally, which cleanly separates it from the sibling list_past_bookings without needing to name it. The ordering hint '(by date, nearest first)' further pins down what the agent gets back.

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 'current/upcoming' framing gives clear context for when this tool applies, and the definition explains the optional-parameter branch (omit provider_id → first venue). It stops short of explicit when-not guidance or naming an alternative such as list_past_bookings, so it is clear context rather than full routing advice.

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