Skip to main content
Glama

generate_booking_card

Read-onlyIdempotent

Get an external search or service link for a destination. Some links are affiliate links.

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
categoryNohotels
languageNoLanguage for the card (en, es, pt)es
destinationYesDestination city

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description earns credit for disclosing that some returned links are affiliate links, but it says nothing about the shape of the result, whether the link is generated or looked up, or what happens for unsupported destinations.

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 short sentences, front-loaded with the outcome and followed by the affiliate disclosure, with no filler. Brevity is close to under-specification, but no sentence is wasted.

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

Completeness2/5

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

There is no output schema, so the description carries the burden of explaining the return value, and it only says 'external search or service link' without describing what a card contains or how category/language affect it. For a tool with seven categories and a language option, this leaves an agent guessing at the artifact it will receive.

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 67% with an enum that documents the category values, so the schema does most of the work. The description adds no meaning about how category or language change the returned link, leaving the one undocumented parameter (category) reliant on its enum alone.

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 gives a concrete outcome: an external search or service link for a destination, which an agent can distinguish from the sibling discovery/planning tools. It drifts from the tool name though — nothing explains what a 'booking card' is or how the link is packaged, so the verb+resource is clear but the artifact is not.

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 only implied: call it when a destination-based booking or service link is needed. There is no statement of when not to use it, no prerequisites, and no routing to the sibling tools even though they are adjacent travel-planning functions.

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