Skip to main content
Glama

Mahonia

by app.mahonia
OverviewDiscussionsAdmin

Search the gear catalog

search_catalog
Read-onlyIdempotent

Fuzzy search of Mahonia's cited gear catalog by brand, product or kind of gear ("duplex", "zpacks", "quilt"). Each result carries a catalog id, the cited weight in grams and whether it is verified. Use get_catalog_product for every variant of one product.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoUp to 25. Default 12.
queryYesTwo characters or more.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe query as searched: trimmed, at most 100 characters.
resultsYesBest first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "query": {
+      "description": "The query as searched: trimmed, at most 100 characters.",
+      "type": "string"
+    },
+    "results": {
+      "description": "Best first.",
+      "items": {
+        "properties": {
+          "brand": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "category": {
+            "description": "The catalog's category: shelter, sleep, pack, and so on.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "display_name": {
+            "description": "Brand, name and variant joined.",
+            "type": "string"
+          },
+          "gear_type": {
+            "description": "What kind of thing it is: Tent, Quilt, Trail runners.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "The catalog row id, the one add_items and create_list take as catalog_id.",
+            "type": "integer"
+          },
+          "kcal": {
+            "description": "Calories per unit, on food.",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "The product name, without brand or variant.",
+            "type": "string"
+          },
+          "variant": {
+            "description": "Size, length or rating; null on a product sold one way.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "verified": {
+            "description": "Whether the cited weight has been verified.",
+            "type": "boolean"
+          },
+          "weight_g": {
+            "description": "The cited weight in grams, to a tenth.",
+            "type": "number"
+          },
+          "weight_source": {
+            "description": "Where the weight comes from.",
+            "enum": [
+              "manufacturer",
+              "measured",
+              "community",
+              "imported"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "variant",
+          "weight_g",
+          "verified",
+          "weight_source",
+          "kcal",
+          "brand",
+          "name",
+          "display_name",
+          "gear_type",
+          "category"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "query",
+    "results"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and an output schema exists, so the description does not need to explain safety or return shape. It still adds real behavioral context: matching is fuzzy rather than exact, and results carry a catalog id plus grams/verified flags. This is useful disclosure beyond the structured fields.

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 what the tool does, then result contents, then the routing hint. Every sentence carries distinct information and there is no padding or repetition.

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?

With annotations covering the safety profile, a full input schema and an output schema, the description only needs to add purpose, matching semantics and sibling routing - all present. Nothing an agent needs to select or invoke this tool correctly 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?

Schema description coverage is 100%, so the baseline is 3 and the schema already documents the two-character minimum and the default/max for limit. The description earns above baseline by giving concrete query examples ('duplex', 'zpacks', 'quilt') that illustrate the expected value space, which the schema does not.

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 and matching behavior ('Fuzzy search'), names the exact resource ('Mahonia's cited gear catalog'), and enumerates the searchable dimensions (brand, product, kind of gear) with concrete example queries. It also names the sibling get_catalog_product and how it differs, so an agent can separate the two without opening either schema.

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?

Explicitly routes multi-variant lookups to get_catalog_product, giving a clear condition that selects the alternative. It stops short of a full when/when-not statement (e.g. what to do when the fuzzy search returns nothing, or how it relates to add_items/create_list workflows), so it is clear context rather than exhaustive guidance.

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

All Mahonia 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