SCVD General Store

Find Something on the Shelf

find_in_catalog

Read-onlyIdempotent

Search this store's shelf and read one item's listing. Returns compact rows — id, name, price in USDC, instant or human-fulfilled, and what the item reads — filtered by a price ceiling, a text match, or both; an item_id returns that one item with its description. Free, read-only, no payment and no account. This is how to learn WHICH item to buy before a buy_* tool, which needs an item_id. Nothing is ranked or recommended: the order is the shelf's own and the filter is a stated rule, printed beside what it matched and what it matched from. NOT a purchase and NOT a stock check.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Words to match against an item's id, name, subtitle and description.
`item_id`	No	One item's id. It replaces search rather than narrowing it: q and max_price_usdc are not applied, and the answer is that one item in full.
`max_price_usdc`	No	A ceiling in USDC. Items at or below it match.

Output Schema

TableJSON Schema

Name	Required	Description
`of`	Yes	How many are on the shelf, the denominator.
`items`	Yes	The rows, in the shelf's own order.
`query`	No	The filter that was applied, echoed.
`matched`	Yes	How many items matched.
`whole_catalogue`	No	The full catalogue, for a caller that wants every field.
`how_this_was_ordered`	No	That the order is the shelf's own and nothing is ranked.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed4 schema fields changedSep 6, 2026

changedInput schema / properties / item_id / description

Previous value: -"One item's id. The answer carries that item alone, in full."New value: +"One item's id. It replaces search rather than narrowing it: q and max_price_usdc are not applied, and the answer is that one item in full."

addedOutput schema / properties / items / items / description
```
Added value: +"One shelf row, in the shelf's own order."
```

addedOutput schema / properties / items / items / properties

Added value: +{
+  "buy_url": {
+    "description": "The x402 door that sells it.",
+    "format": "uri",
+    "type": "string"
+  },
+  "cadence": {
+    "description": "one_off, or the recurring shape.",
+    "type": "string"
+  },
+  "fulfillment": {
+    "description": "instant, or human-fulfilled with a window.",
+    "type": "string"
+  },
+  "id": {
+    "description": "The item id a buy_* call or item_id lookup takes.",
+    "type": "string"
+  },
+  "listing_url": {
+    "description": "The room that describes it in full.",
+    "format": "uri",
+    "type": "string"
+  },
+  "name": {
+    "description": "What the item is called.",
+    "type": "string"
+  },
+  "price_tiers_usdc": {
+    "description": "Every price this item is sold at, cheapest first.",
+    "items": {
+      "type": "number"
+    },
+    "type": "array"
+  },
+  "price_usdc": {
+    "description": "The lowest price on this row, in USDC.",
+    "type": "number"
+  },
+  "reads": {
+    "description": "What the item reads: our_books, subject_fetch, made_here.",
+    "type": "string"
+  },
+  "subtitle": {
+    "description": "The one-line gloss, when the item has one.",
+    "type": "string"
+  }
+}

addedOutput schema / properties / items / items / required

Added value: +[
+  "id",
+  "name",
+  "price_usdc",
+  "cadence",
+  "fulfillment",
+  "reads",
+  "buy_url",
+  "listing_url"
+]

AddedSep 6, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds substantial behavioral context beyond that: the operation is free with no payment or account, nothing is ranked or recommended (order is the shelf's own), the filter is a stated rule printed beside its matches, and item_id replaces rather than narrows the search. This gives the agent an accurate mental model of how results are produced.

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?

The description is dense but information-efficient; every sentence contributes a distinct fact (return format, filter modes, cost model, usage routing, ranking transparency, negative space). The purpose is front-loaded in the first sentence and the buy_* guidance comes early. Minor redundancy exists in the trailing 'NOT a purchase and NOT a stock check' clause, which largely restates what was established earlier, but this is a small cost for unambiguous sibling separation.

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 with an output schema and rich annotations, the description covers return-row contents, filter semantics, cost/account requirements, intended usage relative to buy_* tools, and non-behaviors. The only gaps are minor — no mention of result limits or pagination behavior — and the output schema carries the return-format burden. An agent has everything needed to invoke it correctly.

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 the schema already documents all three parameters, including the item_id override semantics ('It replaces search rather than narrowing it'). The description adds modest interpretive framing — 'filtered by a price ceiling, a text match, or both' — which clarifies how the filters combine, but this is marginal value on top of a complete 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?

Opens with a specific verb+resource pair ('Search this store's shelf and read one item's listing') that clearly states the operation. It further differentiates from siblings by declaring 'NOT a purchase and NOT a stock check' and positioning itself as the prerequisite discovery step before buy_* tools. An agent can distinguish this from buy_human_task, buy_simple, check_order, and verify_artifact without deep schema inspection.

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

Usage Guidelines5/5

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

Explicitly states when to use the tool: 'This is how to learn WHICH item to buy before a buy_* tool, which needs an item_id.' It names the alternative family (buy_*), the condition that selects this tool (needing an item_id before purchasing), and the exclusions ('NOT a purchase and NOT a stock check'). No inference is required on the agent's part.

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

All SCVD General Store tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.