Skip to main content
Glama

Search ToolLoop catalog

search_products
Read-only

USE THIS when a human asks what to buy, or names a tool type but no model number ("I need a router bit set", "cobalt drills under $60", "something for tile"). Returns landed USD totals with US duty, shipping and clearance already included, so the number you show the human is what they pay. Every SKU is returnable for 14 days, no restocking fee; a full refund means the item comes back, and when the fault is ours we pay return shipping (defective items go to an independent inspection facility). Dispatch in 48h, delivery 7-12 days.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
qNokeyword, e.g. 'router bit set', 'cobalt drill', 'tap and die'
limitNo
in_stockNo
ships_toNoUS, CA or GBUS
max_priceNomax landed total in USD
min_priceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses important commercial behavior: prices are landed USD totals including duty, shipping and clearance, plus return and dispatch expectations. These details materially affect how an agent should present results to a human.

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 front-loaded with the usage trigger and examples, and the commercial details are grouped coherently afterward. It is somewhat expansive, especially around returns and inspection, but most sentences still support the shopping use case.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should clarify what search results look like, but it only mentions landed totals and policies. It covers key commercial context well while leaving pagination, result fields, and some parameter behavior undocumented.

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 coverage is 50%, and the description clarifies that price figures are landed totals, which adds meaning for max_price/min_price. However, it does not explain limit, in_stock, or the default behavior of min_price, so it only partly compensates for the schema gaps.

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?

The description clearly frames the tool around human shopping requests and tool types without model numbers, which makes the search intent understandable. It does not explicitly say 'search the catalog' or name the sibling used when a model number is known, so differentiation is implied rather than stated.

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?

It gives a strong when-to-use trigger: a human asks what to buy or names a tool type but no model number, with concrete examples. It does not explicitly name alternatives such as get_product or recommend_for_answer, so the routing guidance is clear but not complete.

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