Skip to main content
Glama

Search the catalogue

search_products
Read-onlyIdempotent

Searches the business’s whole catalogue by the customer’s words, a budget, or both. Returns each product’s current price in INR, options, stock and link, plus the business’s live offers. next_cursor gives the next page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "business": "<business>"
    },
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoProducts per page, 10 if not given.
queryNoWhat the customer wants, in their words, e.g. "oval solitaire ring". Empty lists everything.
cursorNonext_cursor from the previous page.
businessYesThe business id from find_businesses, e.g. "carat-story".
max_priceNoHighest price in INR.
min_priceNoLowest price in INR (rupees, not paise).
collectionNoA collection from list_collections, to narrow the search.
in_stock_onlyNoLeave out sold-out products.

Output Schema

NameRequiredDescriptionDefault
noteNo
offersYes
productsYes
next_cursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world and non-destructive semantics, and the description correctly adds procedural context beyond them: what each result carries (price in INR, options, stock, link, live offers) and that next_cursor drives paging. It does not specify relevance/ranking behavior or empty-result behavior, which keeps it from a 5.

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 is searched, then what comes back, then how to paginate. No redundant or filler wording; each sentence contributes distinct information.

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?

With annotations and a full output schema present, the description does not need to explain return shapes exhaustively, and it covers the key procedural gap (pagination). It leaves collection/in-stock filtering and business-id provenance entirely to the schema, which is acceptable given that schema's completeness.

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 all eight parameters are already documented in the schema, including INR units, defaults and cursor semantics. The description only echoes the query/price combination at a high level and adds no format or constraint detail beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Searches the business's whole catalogue') plus the core selector semantics ('by the customer's words, a budget, or both'). It implicitly separates itself from single-item siblings like get_product by emphasizing 'whole catalogue', though it never names a sibling.

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

Usage Guidelines3/5

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

Usage is only implied through the query/budget framing; there is no explicit when-to-use or when-not-to-use guidance, and no routing to list_collections for browsing or get_product for details. An agent can infer the search use case but gets no exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources