Skip to main content
Glama

VibeBooking

by ai.vibebooking
OverviewDiscussionsAdmin

Get a booking link

book_link
Read-only

The booking link for a stay when you have no offer from get_rates (for example, get_rates could not be read): it re-checks the stay live and opens the hotel's booking page. When you have an offer, give its booking_url instead. Nothing is booked, held or paid here: the traveller books and pays on the hotel's page. Never call it a confirmed booking.

Input Schema

NameRequiredDescriptionDefault
hotelYesThe hotel id from search_hotels or resolve_hotel, or the hotel's website domain.
offerNoNot needed: with an offer from get_rates, give its booking_url instead. An older client's offer id.
totalNoWith offer only: the whole-stay total in minor units.
guestsYesNumber of adult guests.
nightsYesNumber of nights, 1 or more.
checkinYesCheck-in date, YYYY-MM-DD.
childrenNoNumber of children (under 18) in the party; leave out for none.
currencyNoWith offer only: the total's currency, such as JPY.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / children
      Added value: +{
+  "description": "Number of children (under 18) in the party; leave out for none.",
+  "type": "integer"
+}
    • changedInput schema / properties / currency / description
      Previous value: -"With offer: total.currency from get_rates, such as JPY."New value: +"With offer only: the total's currency, such as JPY."
    • changedInput schema / properties / offer / description
      Previous value: -"The offer's id from get_rates; leave out to open the hotel's booking page for the stay."New value: +"Not needed: with an offer from get_rates, give its booking_url instead. An older client's offer id."
    • changedInput schema / properties / total / description
      Previous value: -"With offer: total.minor from get_rates, the whole-stay total in minor units."New value: +"With offer only: the whole-stay total in minor units."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is partly covered. The description goes further by clarifying the real-world semantics: nothing is booked, held, or paid here, payment happens on the hotel's page, and the result must never be called a confirmed booking. It stops short of covering failure modes or live-recheck latency/rate behavior.

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 core purpose and the sibling alternative are front-loaded in the first sentence, with the side-effect disclaimer following. The first sentence is dense and slightly run-on, but no sentence is wasted.

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

Completeness5/5

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

With 8 parameters at full schema coverage, annotations covering the safety profile, and no output schema, the description supplies exactly the missing pieces: when to reach for this tool, what it returns (links to the booking page), and its non-binding semantics. Nothing an agent needs to call it correctly is absent.

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 description coverage is 100% and every parameter (hotel, offer, total, guests, nights, checkin, children, currency) is already documented in the schema. The description's remarks about the offer/booking_url path largely restate the schema's own note on the 'offer' field rather than adding new semantics, so the baseline of 3 applies.

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?

The description names a specific verb+resource ('The booking link for a stay') and explicitly scopes it as the fallback path when 'you have no offer from get_rates'. It contrasts itself with the sibling tool get_rates without requiring the reader to open either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the condition for use ('when you have no offer from get_rates', including the read-failure case) and the condition against use ('When you have an offer, give its booking_url instead'). Both the trigger and the alternative are explicit, leaving nothing to inference.

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

All VibeBooking toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources