Skip to main content
Glama
Sign In
Hotelbeds MCP Server

Hotelbeds MCP Server

by karanrao
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Check rate

check_rate

Re-validate one or more rateKeys before booking to retrieve the authoritative current price when a rate's rateType is RECHECK.

Instructions

Re-validate one or more rateKeys and return the authoritative current price. Required before booking when a rate's rateType is RECHECK.

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": {
      "rateKeys": "<rateKeys>"
    },
    "name": "check_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
rateKeysYesOne or more rateKeys from search_hotels to re-validate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the core trait (re-validation returning current price) and a booking precondition, but omits error behavior, idempotency, auth requirements, and whether the returned price is held.

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?

Two sentences with zero waste. The purpose is front-loaded and immediately followed by the critical booking precondition.

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?

The tool is simple (one required param, full schema coverage), and the description covers its purpose, input source, precondition, and that it returns a current price. It lacks detail on the returned price shape per rateKey and error behavior, but is sufficient for basic invocation.

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 coverage is 100% and the schema description already says 'One or more rateKeys from search_hotels to re-validate.' The tool description repeats this without adding syntax, format, or per-key return meaning, so baseline 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?

States a specific verb (Re-validate) and resource (rateKeys) plus the outcome (authoritative current price). It also distinguishes itself from search_hotels by naming it as the source of rateKeys and from create_booking by stating its precondition role.

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

Usage Guidelines4/5

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

Gives an explicit trigger: 'Required before booking when a rate's rateType is RECHECK.' This clear context tells the agent when to call it, but it does not explicitly state when not to use it or name an alternative for non-RECHECK rates.

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