Skip to main content
Glama

The Builders Supply catalog

Search products

search_products
Read-onlyIdempotent

Full-text search of the store catalog by words, SKU, brand or part number. Returns up to 20 matches with price, availability state and the product page link. For one person's question, not for copying the catalog. Use orderable_only=true to skip items that cannot be bought now.

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": {
      "query": "<query>"
    },
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNobrand name to restrict to, e.g. Schlage
limitNomax results, 1-20, default 10
queryYeswords, SKU or manufacturer part number
offsetNooffset for the next page, default 0
categoryIdNocategory id from list_categories to restrict to
orderableOnlyNotrue = only items that can be ordered now

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavior: a hard cap of 20 matches and what each hit carries (price, availability state, product page link). It does not mention the paging behavior implied by the offset parameter, which is the one behavioral gap.

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 the core verb-resource statement, then return shape, then usage constraints. No filler and nothing repeated from the annotations or schema.

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?

An output schema exists, so return values need no further explanation and the annotations carry the safety profile; the description fills in the result cap and the intended query granularity. The only omission is pagination guidance despite an offset parameter, which is a minor gap for a search tool.

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 six parameters, and this is a baseline-3 case. The description adds only a restatement of the orderable filter and the query surface, and it writes "orderable_only" (snake_case) while the schema key is "orderableOnly", which risks a malformed call rather than clarifying anything.

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 ("full-text search of the store catalog") plus the matchable fields (words, SKU, brand, part number), which clearly separates it from browse_category and get_product by scope. It never names a sibling explicitly, so an agent must infer the boundary rather than being told it.

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 a real exclusion ("For one person's question, not for copying the catalog") and a concrete conditional ("Use orderable_only=true to skip items that cannot be bought now"). It stops short of naming the alternative tool for catalog-wide or category-scoped needs, so the routing is only partially spelled out.

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