Skip to main content
Glama

agentee

by art.allover
OverviewDiscussionsAdmin

Search catalog

search_products
Read-onlyIdempotent

Search the allover.art catalog (one card per design). Args: query? (free text, e.g. 'cat', 'neon koi'), theme? (canonical theme like Cats/Anime/Skulls, comma-separated for several), section? (mens|womens|kids), limit? (<=48), max_price? (USD). Returns product cards with good_id, price and url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax cards to return (default 24, max 48).
queryNoFree-text search, e.g. 'cat' or 'neon koi'.
themeNoCanonical theme filter (Cats, Anime, Skulls, ...); comma-separate several.
sectionNoCatalog section: mens, womens or kids.
max_priceNoOnly items priced at or below this amount, USD.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsNoProduct cards.
totalNoTotal catalog matches for the filters.
showingNoNumber of cards returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Max cards to return (default 24, max 48)."
    • addedInput schema / properties / max_price / description
      Added value: +"Only items priced at or below this amount, USD."
    • addedInput schema / properties / query / description
      Added value: +"Free-text search, e.g. 'cat' or 'neon koi'."
    • addedInput schema / properties / section / description
      Added value: +"Catalog section: mens, womens or kids."
    • addedInput schema / properties / theme / description
      Added value: +"Canonical theme filter (Cats, Anime, Skulls, ...); comma-separate several."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "items": {
+      "description": "Product cards.",
+      "items": {
+        "properties": {
+          "code": {
+            "type": "string"
+          },
+          "currency": {
+            "type": "string"
+          },
+          "good_id": {
+            "type": "integer"
+          },
+          "image": {
+            "type": "string"
+          },
+          "price": {
+            "type": "number"
+          },
+          "product": {
+            "type": "string"
+          },
+          "theme": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "description": "Canonical product page.",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "showing": {
+      "description": "Number of cards returned.",
+      "type": "integer"
+    },
+    "total": {
+      "description": "Total catalog matches for the filters.",
+      "type": "integer"
+    }
+  },
+  "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 provide safety traits (readOnly, idempotent, non-destructive). Description adds return format behavior (product cards with good_id, price, url) and design constraint (one card per design). No contradiction.

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 sentences with no wasted words. Front-loaded with purpose, then parameter list, then return format. Efficient and clear.

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?

Covers search scope, all parameters with usage hints, and return fields. With output schema present, this is complete for a search tool. No missing context.

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 coverage is 100%. Description adds examples for query, theme, section, and clarifies limit max and currency. This enhances the schema's parameter descriptions.

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 tool searches the allover.art catalog with specific verb 'Search' and resource 'catalog', and adds nuance 'one card per design'. It distinguishes from siblings like 'get_product' implicitly.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool vs alternatives (e.g., get_product). Parameter usage hints are given but not usage context. Agent must infer.

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

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