Skip to main content
Glama
Sign In

public

by com.kratons
OverviewDiscussionsAdmin

Search experiences

search_experiences
Read-only

Tours and tickets Kratons operates, filtered by country, city and free text. Returns { experiences: [...] } with name, type, city, country, category, duration, free-cancellation flag and a summary — never prices or suppliers (Kratons quotes one package price per trip).

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": "search_experiences"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoFree-text search on name, description and tags
cityNoCity name, e.g. Madrid, Lisbon, Marrakech
limitNoMax results (default 20, max 50)
countryNoCountry name, e.g. Spain, Portugal, Morocco

Output Schema

NameRequiredDescriptionDefault
experiencesYesNever prices or suppliers — one package price per trip, quoted by a human

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": {
+    "experiences": {
+      "description": "Never prices or suppliers — one package price per trip, quoted by a human",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "category": {
+            "anyOf": [
+              {
+                "enum": [
+                  "private",
+                  "small_group",
+                  "group"
+                ],
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "city": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "country": {
+            "$ref": "#/properties/experiences/items/properties/city"
+          },
+          "durationMinutes": {
+            "anyOf": [
+              {
+                "type": "integer"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "freeCancellation": {
+            "type": "boolean"
+          },
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "summary": {
+            "type": "string"
+          },
+          "type": {
+            "enum": [
+              "Tour",
+              "Ticket"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "type",
+          "city",
+          "country",
+          "category",
+          "durationMinutes",
+          "freeCancellation",
+          "summary"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "experiences"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the read-only annotation, the description discloses a specific behavioral guarantee: results never include prices or suppliers because Kratons quotes one package price per trip. It also pre-declares the response shape. This is meaningful added context, though it does not cover pagination or error behavior.

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 sentences with no filler; the core purpose and filters come first, followed by the return-shape caveat. It earns its place, but the first sentence's phrasing ('Tours and tickets Kratons operates') is slightly awkward and could be tightened.

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?

For a read-only search tool, the description covers the object scope, filters, output fields, and the most important exclusion (no price/supplier details). With the output schema and annotations already present, nothing essential is missing for a typical call, though sort/pagination behavior is not mentioned.

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% and each parameter already has a clear description. The tool description only restates that the search is filtered by country, city, and free text, adding no semantic detail beyond the schema. Baseline 3 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 identifies a specific action and resource: searching the tours and tickets Kratons operates, with explicit filters (country, city, free text). This clearly separates it from the sibling tools, which deal with destinations, itineraries, or proposal requests.

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 filter list and the 'Tours and tickets Kratons operates' scope imply the intended use case, but there is no explicit when-to-use/when-not-to-use or contrast with alternatives like list_destinations or list_sample_itineraries. The context is clear enough to infer usage, but the routing burden is left to the agent.

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