Skip to main content
Glama
forgemeshlabs

Travel Assistant MCP

by forgemeshlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

build_booking_link

Read-onlyIdempotent

Generate an external booking link for a selected route after route details are known. Returns a commission-eligible URL without completing the booking.

Instructions

Generate only an external booking link for an already chosen route. Use after route details are known or after compare_routes/search_travel_options; do not use as the first step when the user still needs search guidance. Read-only, no authentication, no booking completion, and no reservation side effects. The returned link may be commission-eligible and is disclosed in output.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
originNoOrigin IATA code (e.g. 'IAH'). Case-insensitive.
currencyNoISO 4217 currency code (default: USD).
destinationNoDestination IATA code (e.g. 'CDG'). Case-insensitive.
return_dateNoReturn date in YYYY-MM-DD format. Optional — omit for one-way.
departure_dateNoDeparture date in YYYY-MM-DD format. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / currency / description
      Previous value: -"Currency code"New value: +"ISO 4217 currency code (default: USD)."
    • changedInput schema / properties / departure_date / description
      Previous value: -"Departure date YYYY-MM-DD"New value: +"Departure date in YYYY-MM-DD format. Optional."
    • changedInput schema / properties / destination / description
      Previous value: -"Destination airport code"New value: +"Destination IATA code (e.g. 'CDG'). Case-insensitive."
    • changedInput schema / properties / origin / description
      Previous value: -"Origin airport code"New value: +"Origin IATA code (e.g. 'IAH'). Case-insensitive."
    • changedInput schema / properties / return_date / description
      Previous value: -"Return date YYYY-MM-DD"New value: +"Return date in YYYY-MM-DD format. Optional — omit for one-way."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Adds behavioral context beyond annotations: read-only, no authentication, no booking completion, no reservation side effects, commission-eligible, link disclosed. Annotations already declare safety profile, but description enriches it.

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?

Four sentences, each essential. Front-loaded with purpose. No wasted words.

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?

Tool is simple; schema fully describes parameters. Description covers behavior, usage context, and no output schema needed. Complete for its purpose.

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 baseline is 3. Description does not add parameter-specific details beyond schema, but overall context is sufficient.

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?

Clearly states verb 'generate', resource 'external booking link', and context 'for an already chosen route'. Differentiates from sibling tools by specifying it is for after route details are known.

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?

Explicitly says to use 'after route details are known' and 'do not use as the first step when the user still needs search guidance'. Provides clear context for use.

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