Skip to main content
Glama
Sign In

public

by com.kratons
OverviewDiscussionsAdmin

Sample itineraries

list_sample_itineraries
Read-only

Published sample itineraries Kratons operates, as { itineraries: [...] } (name, destination, duration, category, summary, day-by-day outline) to start a conversation from. Never prices or suppliers — every trip is quoted as one package price by a human advisor.

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_sample_itineraries"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoFree text on name, summary and tags
limitNoMax results (default 20, max 50)
countryNoDestination filter, e.g. Portugal, Andalusia

Output Schema

NameRequiredDescriptionDefault
itinerariesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "itineraries": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "category": {
+            "type": "string"
+          },
+          "days": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "day": {
+                  "description": "1-based day number",
+                  "type": "integer"
+                },
+                "items": {
+                  "items": {
+                    "additionalProperties": false,
+                    "properties": {
+                      "kind": {
+                        "type": "string"
+                      },
+                      "label": {
+                        "type": "string"
+                      }
+                    },
+                    "required": [
+                      "kind",
+                      "label"
+                    ],
+                    "type": "object"
+                  },
+                  "type": "array"
+                }
+              },
+              "required": [
+                "day",
+                "items"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "destination": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "durationDays": {
+            "anyOf": [
+              {
+                "type": "integer"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "pricing": {
+            "description": "The pricing note: one package price per trip, no public price list",
+            "type": "string"
+          },
+          "summary": {
+            "$ref": "#/properties/itineraries/items/properties/destination"
+          },
+          "tags": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "destination",
+          "durationDays",
+          "category",
+          "tags",
+          "summary",
+          "days",
+          "pricing"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "itineraries"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/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 adds valuable behavioral context: the result shape and the guaranteed absence of prices or suppliers. This goes beyond what annotations alone provide, though it omits deeper operational details like rate limits or authentication, which are not critical for a simple read-only listing.

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?

Two front-loaded sentences carry the core action, return shape, and a key content boundary without any wasted words. The structure is tight and every clause earns its place.

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 low-complexity, read-only tool with optional filters and an output schema, the description plus annotations fully cover what an agent needs to call it correctly. The explicit statement about no prices or suppliers removes a likely source of agent confusion.

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?

All three parameters (q, limit, country) have schema descriptions and coverage is 100%, so the description does not need to add parameter semantics. The description's mention of the destination field loosely aligns with the country filter, but it adds no parameter-specific detail beyond the schema.

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 clearly identifies the resource (published sample itineraries) and the action (list), and even specifies the return shape as { itineraries: [...] }. It does not explicitly contrast this with siblings like search_experiences or list_destinations, so it misses the full differentiation criterion for a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a concrete usage context: these itineraries are 'to start a conversation from,' and it explicitly warns that prices and suppliers are never included. It does not name alternative tools or state when not to use this tool, so it falls short of explicit routing guidance.

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

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