EcoAloha

Search published catalog

search_catalog

Read-onlyIdempotent

Search published destinations and collections by keyword. Returns existing text, not live offers or generated answers.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 19, 2026

addedOutput schema / anyOf

Added value: +[
+  {
+    "properties": {
+      "results": {
+        "items": {
+          "properties": {
+            "description": {
+              "type": "string"
+            },
+            "name": {
+              "type": "string"
+            },
+            "schema_object": {
+              "type": "object"
+            },
+            "score": {
+              "maximum": 100,
+              "minimum": 0,
+              "type": "number"
+            },
+            "site": {
+              "type": "string"
+            },
+            "url": {
+              "format": "uri",
+              "type": "string"
+            }
+          },
+          "required": [
+            "url",
+            "name",
+            "description",
+            "site",
+            "score",
+            "schema_object"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "results"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "availableTools": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "code": {
+        "type": "string"
+      },
+      "docs": {
+        "format": "uri",
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      },
+      "retryAfterSeconds": {
+        "type": "integer"
+      },
+      "status": {
+        "type": "integer"
+      }
+    },
+    "required": [
+      "code",
+      "message",
+      "status"
+    ],
+    "type": "object"
+  }
+]

removedOutput schema / properties

Removed value: -{
-  "results": {
-    "items": {
-      "properties": {
-        "description": {
-          "type": "string"
-        },
-        "name": {
-          "type": "string"
-        },
-        "schema_object": {
-          "type": "object"
-        },
-        "score": {
-          "maximum": 100,
-          "minimum": 0,
-          "type": "number"
-        },
-        "site": {
-          "type": "string"
-        },
-        "url": {
-          "format": "uri",
-          "type": "string"
-        }
-      },
-      "required": [
-        "url",
-        "name",
-        "description",
-        "site",
-        "score",
-        "schema_object"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  }
-}

removedOutput schema / required
```
Removed value: -[
-  "results"
-]
```

First observedSep 6, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds valuable behavioral context by clarifying that results are existing text, not dynamically generated or live content.

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 well-structured sentence with no filler. It front-loads the action and resource, then adds a useful clarifying contrast about the return content.

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?

Given the simple single-parameter schema, the presence of an output schema, and annotations covering safety and idempotency, the description is complete. It captures purpose, scope, and a key behavioral distinction without unnecessary detail.

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 description coverage is 0%, but the description's 'by keyword' phrase clearly conveys the semantic of the single required query parameter. With only one simple string parameter, this is sufficient; no further parameter disambiguation is needed.

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 states a specific verb ('Search'), a clear resource ('published destinations and collections'), and a keyword mechanism. It further distinguishes itself by noting it returns existing text rather than live offers or generated answers.

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 clearly signals when to use the tool by scoping it to published destinations and collections and by excluding live offers or generated answers. It does not explicitly name alternatives like search_experiences, but the scope is clear enough for an agent to infer the boundary.

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

All EcoAloha 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.