Skip to main content
Glama

Sorted Travel

render_recommended_destinations

Read-onlyIdempotent

Render the destination recommendations carousel.

Paired data tool: get_recommended_destinations. Input is that tool's destinations list (full list for a new search, or a filtered subset for follow-ups such as cheapest or visa-free) plus related fields from the same result. Hosts show the carousel from this render tool; the data tool alone does not. Do not invent destination cards.

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": {
      "destinations": "<destinations>"
    },
    "name": "render_recommended_destinations"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsNoMonths from the recommendation result.
statusNoResult status. Usually OK.OK
messageNoOptional status message for empty or error states.
currencyNoCurrency code from the recommendation result.USD
total_cntNoTotal match count from the recommendation result.
destinationsYesDestination cards from get_recommended_destinations. Pass the full list, or a filtered subset for follow-ups such as cheapest or visa-free.
discover_urlNoDiscover URL from the recommendation result.
source_location_codeNoDeparture IATA from the recommendation result `from` field.LHR
selected_month_indexesNoSelected month indexes from the recommendation result.

Output Schema

NameRequiredDescriptionDefault
fromNoDeparture IATA airport code.LHR
monthsNoTravel months from the recommendation result.
statusYesResult status. Usually OK.
messageNoOptional status message for empty or error states.
currencyNoCurrency code for prices.USD
total_cntNoTotal match count from the recommendation result.
destinationsYesDestination cards shown in the carousel.
discover_urlNoDiscover page URL for the same search.
selected_month_indexesNoSelected month indexes from the recommendation result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "description": "Structured content returned by render_recommended_destinations.",
      +  "properties": {
      +    "currency": {
      +      "default": "USD",
      +      "description": "Currency code for prices.",
      +      "title": "Currency",
      +      "type": "string"
      +    },
      +    "destinations": {
      +      "description": "Destination cards shown in the carousel.",
      +      "items": {
      +        "additionalProperties": true,
      +        "type": "object"
      +      },
      +      "title": "Destinations",
      +      "type": "array"
      +    },
      +    "discover_url": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "description": "Discover page URL for the same search.",
      +      "title": "Discover Url"
      +    },
      +    "from": {
      +      "default": "LHR",
      +      "description": "Departure IATA airport code.",
      +      "title": "From",
      +      "type": "string"
      +    },
      +    "message": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "description": "Optional status message for empty or error states.",
      +      "title": "Message"
      +    },
      +    "months": {
      +      "anyOf": [
      +        {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "description": "Travel months from the recommendation result.",
      +      "title": "Months"
      +    },
      +    "selected_month_indexes": {
      +      "anyOf": [
      +        {
      +          "items": {
      +            "type": "integer"
      +          },
      +          "type": "array"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "description": "Selected month indexes from the recommendation result.",
      +      "title": "Selected Month Indexes"
      +    },
      +    "status": {
      +      "description": "Result status. Usually OK.",
      +      "title": "Status",
      +      "type": "string"
      +    },
      +    "total_cnt": {
      +      "anyOf": [
      +        {
      +          "type": "integer"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "description": "Total match count from the recommendation result.",
      +      "title": "Total Cnt"
      +    }
      +  },
      +  "required": [
      +    "status",
      +    "destinations"
      +  ],
      +  "title": "RecommendationsRenderOutput",
      +  "type": "object"
      +}
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the render-vs-data distinction: the carousel is only displayed when this tool is called. The 'do not invent destination cards' constraint is a genuine behavioral rule not present in structured fields, though it says nothing about empty/error rendering beyond the schema's status/message fields.

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 short sentences, front-loaded with the pairing that determines correct usage, and every sentence carries a distinct instruction (what it does, what feeds it, why the render tool is needed, what not to do). No filler.

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?

With 9 parameters, 100% schema coverage and an output schema, the description only needs to explain the data-flow contract, which it does clearly. Slight gap: it does not mention how status/message fields should be set for empty or error states, leaving that entirely to the schema.

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%, so all nine parameters are already documented individually; the description only adds the framing that destinations come from get_recommended_destinations and are passed through with 'related fields from the same result'. That is a useful but modest supplement, matching the baseline-3 case where the schema does the heavy lifting.

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 and resource ('Render the destination recommendations carousel') and immediately names the paired data tool get_recommended_destinations, so an agent can tell it apart from the get_* siblings without opening a schema.

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?

Gives explicit when-to-use context: the input is the data tool's destinations list, full for a new search or a filtered subset for follow-ups like cheapest or visa-free. It also states the consequence of skipping it ('hosts show the carousel from this render tool; the data tool alone does not') and closes with a constraint ('Do not invent destination cards').

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.