OwnerRez MCP Server

get_booking

Retrieve complete booking details by OwnerRez ID, optionally including guest information.

Instructions

Get full details for a single booking by its OwnerRez 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

Name	Required	Description	Default
`booking_id`	Yes
`include_guest`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Aug 23, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Get' conveys a read operation, but this merely restates the tool name; it does not disclose side effects, error behavior, permissions, or the effect of include_guest on the response. The description adds no meaningful behavioral context beyond the verb.

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 sentence with no redundant words; the key identifier and scope are front-loaded. It is appropriately concise, though the brevity leaves some semantic gaps that could be addressed without bloating the description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema covers return values, but the description is incomplete for an agent: include_guest is entirely unexplained, and there is no guidance about when to use this tool versus list_bookings. For a simple two-parameter getter, the missing include_guest semantics is a meaningful gap.

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?

Schema description coverage is 0%, so the description must compensate. It adds meaning to booking_id ('OwnerRez ID') but says nothing about include_guest, which is undocumented in the schema and whose behavioral impact (including guest details) is left entirely to inference.

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 ('Get'), a precise resource ('single booking'), and the required identifier ('OwnerRez ID'). This clearly distinguishes it from siblings like list_bookings, which returns multiple bookings, and who_is_staying, which focuses on current guests.

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?

The phrase 'single booking by its OwnerRez ID' implies it is for retrieving one known booking rather than listing many, but the description does not explicitly say when to prefer this over list_bookings or mention any alternatives. Usage context is present but only implicitly.

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

Deploy Server