Rezdy Agent MCP Server

rezdy_agent_get_booking

Retrieve Rezdy booking details by ID to access customer data, payment status, and reservation information. Manage travel bookings and agent workflows with targeted lookup capabilities.

Instructions

Get details of a specific booking

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": {
      "bookingId": "<bookingId>"
    },
    "name": "rezdy_agent_get_booking"
  }
}

Input Schema

Name	Required	Description	Default
`bookingId`	Yes	Booking ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 5, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. While 'Get' implies a read-only operation, the description does not specify error handling (e.g., booking not found), rate limits, caching behavior, or data sensitivity concerns.

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?

The single sentence is efficient and front-loaded with no wasted words. However, given the absence of annotations and output schema, the extreme brevity leaves critical gaps in behavioral and return-value documentation.

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 simple single-parameter retrieval tool, the description provides the minimum viable context. However, without an output schema, it should ideally characterize what 'details' are returned (e.g., customer info, status, product details) to be fully complete.

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?

With 100% schema description coverage, the schema already fully documents the bookingId parameter. The description adds no additional parameter semantics (e.g., ID format, where to obtain it), warranting the baseline score of 3.

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 uses a clear verb ('Get') and resource ('booking'), and the word 'specific' implies a single-record lookup distinguishing it from search operations. However, it does not explicitly differentiate from sibling tools like update_booking or create_booking.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., when to use get_booking vs search_availability) and does not mention prerequisites like needing a valid booking ID from prior operations.

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

Deploy Server