Skip to main content
Glama

Casona Hoteles Boutique — Live Hotel Rates

Search Casona Room Quotes

search_casona_room_quotes
Read-onlyIdempotent

Check live SiteMinder room availability and full-stay room rates in COP excluding 19% Colombian VAT for either or both Casona hotels. Also returns the tax-inclusive amount for verification, plus room/rate names and date-prefilled direct-booking links. No booking is created; guest must confirm rates and terms in the hotel booking engine.

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": {
      "checkIn": "<checkIn>",
      "checkOut": "<checkOut>"
    },
    "name": "search_casona_room_quotes"
  }
}

Input Schema

NameRequiredDescriptionDefault
hotelNoHotel: either Casona, or both (default).
adultsNoNumber of adults, default 2.
checkInYesGuest arrival date YYYY-MM-DD, Cartagena local time.
infantsNoNumber of infants, default 0.
checkOutYesGuest departure date YYYY-MM-DD; 1–31 nights.
childrenNoNumber of children, default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly=true, idempotent=true, nondestructive, and closed-world, so the description's marginal value is in the pricing detail: rates are in COP excluding 19% Colombian VAT and a tax-inclusive figure is returned for verification. It also discloses the return contents (room/rate names, date-prefilled booking links) and repeats that no booking is created, which adds moderate context without covering caching or live-data staleness.

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 live availability/rate check, followed by return contents and the no-booking disclaimer. Dense but each clause carries information; minor redundancy with the readOnly annotation in 'No booking is created'.

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 six-parameter read-only search with no output schema, the description covers what is checked, the currency and tax treatment, and what is returned, which is enough to call it correctly. It does not describe empty-result or sold-out behavior, a small remaining 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 description coverage is 100%, with each parameter (including the hotel enum and occupancy minimums/maximums) already documented in the schema. The description adds only the phrase 'either or both Casona hotels', which restates the enum rather than deepening parameter meaning.

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 names a specific verb and resource: it checks live SiteMinder room availability and full-stay rates for the Casona hotels, and the scope ('either or both Casona hotels') is stated. The only sibling, list_casona_properties, is never named, so the agent gets no explicit differentiation between searching quotes and listing properties.

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?

Usage is implied rather than stated: the tool is for checking availability and rates before booking, and the closing sentence clarifies that no booking is created. There is no explicit 'use this instead of X' routing, nor any exclusion such as minimum-stay or same-day constraints beyond what the schema encodes.

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