Sorted Travel

render_destination_info

Read-onlyIdempotent

Render the destination facts card.

Always call get_destination_info first, then pass its structuredContent here. Do not invent destination facts.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`destination`	Yes	Full structuredContent from get_destination_info. Pass it through unchanged.

Output Schema

TableJSON Schema

Name	Required	Description
`name`	No	Destination display name.
`brief`	No	Short on-the-ground destination brief.
`handle`	No	Sorted sitemap handle such as paris or tokyo.
`status`	Yes	Result status. Usually OK.
`sunset`	No	Today's local sunset as HH:MM.
`country`	No	Country name.
`message`	No	Optional status message for empty or error states.
`sunrise`	No	Today's local sunrise as HH:MM.
`ui_view`	No	Widget view. place for destination facts.
`image_url`	No	Destination photo URL for the place card hero image.
`place_url`	No	Full destination page URL on sorted.travel.
`best_time_summary`	No	Short best-time-to-visit overview shown on the place card.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026

addedOutput schema / properties / image_url

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Destination photo URL for the place card hero image.",
+  "title": "Image Url"
+}

Changed3 schema fields changedSep 27, 2026

addedOutput schema / properties / best_time_summary

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Short best-time-to-visit overview shown on the place card.",
+  "title": "Best Time Summary"
+}

addedOutput schema / properties / sunrise

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Today's local sunrise as HH:MM.",
+  "title": "Sunrise"
+}

addedOutput schema / properties / sunset

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Today's local sunset as HH:MM.",
+  "title": "Sunset"
+}

Changed1 schema field changedSep 26, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Structured content returned by render_destination_info.",
+  "properties": {
+    "brief": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Short on-the-ground destination brief.",
+      "title": "Brief"
+    },
+    "country": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Country name.",
+      "title": "Country"
+    },
+    "handle": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Sorted sitemap handle such as paris or tokyo.",
+      "title": "Handle"
+    },
+    "message": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Optional status message for empty or error states.",
+      "title": "Message"
+    },
+    "name": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Destination display name.",
+      "title": "Name"
+    },
+    "place_url": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Full destination page URL on sorted.travel.",
+      "title": "Place Url"
+    },
+    "status": {
+      "description": "Result status. Usually OK.",
+      "title": "Status",
+      "type": "string"
+    },
+    "ui_view": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Widget view. place for destination facts.",
+      "title": "Ui View"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "title": "PlaceRenderOutput",
+  "type": "object"
+}

AddedSep 26, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral value beyond them: the mandatory upstream dependency on get_destination_info and the requirement to pass structuredContent unchanged, which prevents the agent from synthesizing its own input.

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?

Three short sentences, front-loaded with the action, then the precondition, then the guardrail. Nothing extraneous; every sentence carries a distinct instruction.

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?

Output schema exists so return values need no explanation, annotations cover the safety profile, and the single parameter is fully documented. The remaining thing an agent needs — the required call ordering and no-fabrication rule — is present in the description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already states the parameter is the full structuredContent from get_destination_info, so the baseline is 3. The description reinforces the provenance constraint and adds the 'pass it through unchanged' rule, giving semantics beyond the type definition.

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+resource ('Render the destination facts card'), which cleanly separates it from the sibling render_* tools (weather, recommended destinations). An agent can identify the tool's job without opening the 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 an explicit precondition ('Always call get_destination_info first') and an explicit prohibition ('Do not invent destination facts'), which tells the agent exactly when this tool applies and when its input is invalid. This is a complete usage contract, not just implied context.

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

All Sorted Travel tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?