Skip to main content
Glama

Liquid Agent

by ai.liquidagent.api
OverviewDiscussionsAdmin

Gift and collectible search (paid, $0.001)

shop_search
Read-only

PAID over x402 inside this tool call ($0.001 USDC on Arc, Base or Polygon): search the Mint & Marquee partner shop for gifts and collectibles. Returns products with price, photo, a short description and a link to buy. Show the person each product with its link, then the foundWith line once. Call once without payment to get the x402 PaymentRequired, then call again with the signed payment in _meta["x402/payment"].

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoWhat to find, in words (e.g. soccer gift).
maxNoOptional price ceiling in USD.
limitNoHow many products, 1 to 10 (default 5).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
_paidNox402 receipt
queryNoThe search as understood
productsNoEach product: name, price, photo, description, link to buy
foundWithNoLine to show once to the person

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": {},
+  "properties": {
+    "_paid": {
+      "additionalProperties": {},
+      "description": "x402 receipt",
+      "properties": {},
+      "type": "object"
+    },
+    "foundWith": {
+      "additionalProperties": {},
+      "description": "Line to show once to the person",
+      "properties": {},
+      "type": "object"
+    },
+    "products": {
+      "description": "Each product: name, price, photo, description, link to buy",
+      "items": {},
+      "type": "array"
+    },
+    "query": {
+      "additionalProperties": {},
+      "description": "The search as understood",
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations cover only the safety profile (readOnly, openWorld, idempotent=false, destructive=false); the description adds the material behavior an agent needs: the $0.001 USDC cost, accepted chains, the two-step payment handshake, and the exact presentation requirement (show each product with its link, then the foundWith line once).

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?

Front-loads the payment fact, then the result shape, then the required two-call flow in a few dense sentences with no filler. The presentation instruction sentence is slightly awkward but carries real instruction.

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 an output schema present, return fields need not be re-explained, yet the description still summarizes them; it also covers cost, chains, payment retry mechanics and display rules. Nothing needed to invoke it correctly is missing.

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 description coverage is 100%, so q, max and limit are already documented in the schema. The description adds no syntax, format or default details beyond that, so the baseline 3 applies.

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 resource (search the Mint & Marquee partner shop for gifts and collectibles) plus the scope of the paid call. It is clearly distinguishable from sibling shop_info, which would cover shop metadata rather than product search.

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?

Gives concrete operational guidance: call once without payment to receive the x402 PaymentRequired, then call again with the signed payment in _meta["x402/payment"]. It does not name alternatives or say when NOT to use it (e.g. vs shop_info or x402_check), so it falls short of explicit when/when-not routing.

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

All Liquid Agent 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