public

Destinations with experiences

list_destinations

Read-only

Countries and cities where Kratons currently offers tours or tickets, with counts. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_destinations"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`countries`	Yes
`generatedAt`	Yes	ISO timestamp of the underlying query (cached for an hour)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "countries": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "cities": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "city": {
+                  "type": "string"
+                },
+                "experienceCount": {
+                  "type": "integer"
+                }
+              },
+              "required": [
+                "city",
+                "experienceCount"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "country": {
+            "type": "string"
+          },
+          "experienceCount": {
+            "type": "integer"
+          }
+        },
+        "required": [
+          "country",
+          "experienceCount",
+          "cities"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "generatedAt": {
+      "description": "ISO timestamp of the underlying query (cached for an hour)",
+      "type": "string"
+    }
+  },
+  "required": [
+    "countries",
+    "generatedAt"
+  ],
+  "type": "object"
+}

First observedSep 16, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description redundantly says 'Read-only.' It adds minimal extra context, such as 'with counts' and 'currently offers,' which hint at the output content but not any additional behavioral constraints like rate limits or auth requirements. No contradiction with annotations.

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?

The description is a single concise sentence that immediately states the purpose and scope, with no filler. It is front-loaded and efficient, making it easy for an agent to parse quickly.

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?

For a zero-parameter, read-only list tool with an output schema present, the description covers everything needed: what is listed, that it includes counts, and that it is read-only. The output schema handles return format details. Nothing essential is missing.

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?

The tool has zero parameters, so the description does not need to explain parameter semantics. The schema is empty (100% coverage), and the baseline for no parameters is 4. The description adds no parameter-related information, which is appropriate.

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?

The description clearly states the resource (destinations) and what it provides (countries/cities with counts of tours or tickets). It is unambiguous and distinct from sibling tools, which all focus on proposals, itineraries, or company facts. The verb 'list' is implied by the name and reinforced by the description.

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?

The usage is implied by the description—an agent would naturally call this to get available destinations—but there is no explicit guidance on when to choose it over alternatives or any exclusions. Since it's a simple zero-parameter listing, this is acceptable but not exemplary.

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

All public 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?