Skip to main content
Glama

generate_booking_card

Read-onlyIdempotent

Generates a localized booking recommendation card by destination and travel category, showing verified hotel, activity, flight, transfer, and eSIM options.

Instructions

Curate verified booking recommendations across soulful boutique hotels, historic quiet retreats, authentic local experiences, and seamless travel mobility.

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": {
      "destination": "<destination>"
    },
    "name": "generate_booking_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoService category (hotels, activities, flights, esim, transfers, luggage, compensation, insurance)hotels
languageNoLanguage for the card (en, es, pt)es
destinationYesDestination city
experience_titleNoOptional specific experience or stay title

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.9.4

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description adds nothing on top of it. It does not explain what 'generate' produces, whether results are cached/idempotent by destination+category, whether 'verified' implies a filtering guarantee or a live availability check, or what happens on an unknown destination. The marketing adjectives ('soulful', 'seamless') consume the space that behavioral detail should occupy.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence, which is efficient, but nearly all of it is promotional filler rather than front-loaded operational information. Words like 'verified', 'soulful', 'historic quiet' and 'seamless' do not help an agent decide or invoke. Nothing is wasted on length, but much is wasted on tone.

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: four flat parameters, one required, full schema coverage, no nested objects and no output schema. The description enumerates the product categories it covers, which is roughly the minimum an agent needs to pick it. Return format is undefined but there is no output schema to lean on, so the gap is tolerated rather than ideal.

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%, so the baseline is 3 and the schema already explains category, language, destination and experience_title. The description's list of categories loosely echoes the category parameter but names different wording (e.g. 'travel mobility' vs. the enum-like transfers/luggage/esim values), which adds flavor rather than usable mapping. It offers no guidance on the default category 'hotels' or on how language affects output.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb is 'curate' and the object is 'booking recommendations', which suggests discovery rather than the generation of a card implied by the name. The enumerated categories (boutique hotels, retreats, local experiences, travel mobility) do hint at an inventory of bookable products, but a reader still cannot tell whether the tool returns links, a rendered card, or a booked reservation. It is not clearly distinguished from siblings such as discover_secret_haven or explore_sensory_earth, which read as overlapping discovery verbs.

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?

There is no statement of when to call this tool, no prerequisite (e.g. destination already chosen, category selection), and no exclusion or named alternative. The phrase 'curate ... recommendations' could equally describe any of the four sibling tools. An agent must guess from the name alone that this builds a presentable card rather than performing a search.

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