Skip to main content
Glama
Sign In
booking_chest

booking_chest

by dsddet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_booking

Retrieve a specific booking's details by providing its unique booking ID. Use this to look up or confirm booking information.

Instructions

Get a booking by ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "booking_id": "<booking_id>"
    },
    "name": "get_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
booking_idYesBooking ID

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. 'Get' implies a non-destructive read operation, but it does not disclose what is returned (though output schema exists), any error conditions (e.g., what happens with an invalid ID), or whether it requires authentication. Baseline is 3 as it doesn't mislead but lacks depth.

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

Conciseness5/5

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

The description is a single, concise sentence with no wasted words. It is front-loaded with the key action and resource. For a tool with one parameter and an output schema, this level of brevity is ideal.

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?

Given the tool's simplicity (one param, output schema present), the description is minimally complete for a basic lookup. However, it could mention that the output contains booking details, though the output schema technically covers that. It lacks any error context or ID validation hints.

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?

The input schema has 100% description coverage with a single required param (booking_id). The description 'Get a booking by ID' merely echoes the schema's 'Booking ID' description, adding no new semantics like expected format or constraints (e.g., integer range). Baseline 3 is appropriate.

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 clearly states the action (get) and the resource (booking by ID). It distinguishes itself from sibling tools like list_bookings (which lists multiple bookings) and cancel_booking (which modifies a booking). The 'by ID' qualifier adds specificity.

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?

No guidance is provided on when to use this vs alternatives. For example, it doesn't mention that list_bookings would be appropriate for fetching multiple bookings or filtering, nor does it state any prerequisites like needing the booking ID beforehand.

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