Skip to main content
Glama

Search products by spec

search_products
Read-onlyIdempotent

Filters verified products in one category by spec values (for example watts, weight, ports, capacity) and returns up to 10, each with its source URL and check date. Numeric filters use min/max objects keyed by field name; yes/no filters use flags. Every response lists the fields that category can be filtered and sorted on. Products with an unknown value for a filtered field are left out. Recalled products are not included.

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

Input Schema

NameRequiredDescriptionDefault
maxNoOptional. Maximum values as an object of {numeric field name: number}; a product passes when the field is at most that number. Same field names as min. Products with no value for the field are excluded. Example: {"weight_g": 300}.
minNoOptional. Minimum values as an object of {numeric field name: number}; a product passes when the field is at least that number. Field names end in their unit (_w watts, _g grams, _mm millimetres, _mah, _gbps). Valid names depend on the category and are listed in every response under filterable_fields.numeric. Products with no value for the field are excluded. Example: {"total_output_w": 100, "usb_c_ports": 2}.
langNoLanguage of text fields (notes, labels, answers). One of: "en" (English), "zh-hant" (Traditional Chinese), "zh-hans" (Simplified Chinese). Default "en". Spec values and model numbers are the same in every language. Example: "zh-hant".en
brandNoOptional. Brand name, matched exactly but ignoring case and spacing. Up to 60 characters. No default (all brands). Example: "Anker" or "UGREEN".
flagsNoOptional. Yes/no conditions as an object of {boolean field name: true or false}. Valid names depend on the category and are listed in every response under filterable_fields.yes_no. Example: {"pd31_epr": true} for chargers, {"flight_ok": true} for power banks.
limitNoMaximum number of products to return: a whole number from 1 to 10. Default 10. The response also gives total_matches. Example: 5.
orderNoSort direction when sort_by is set: "asc" (smallest first) or "desc" (largest first). Default "asc". Example: "desc" with sort_by "total_output_w" for the most powerful first.asc
queryNoOptional. Space-separated words that must all appear in the product name, model number or other model numbers; case is ignored. Up to 120 characters. No default. Example: "Prime 160W" or "A2687".
sort_byNoOptional. One numeric field name to sort results by (same names as min and max). Products with no value for that field are left out when sorting. No default: without it, results keep the site's own order. Example: "weight_g".
categoryYesRequired. The one product category to search, as a slug. One of: "chargers", "power-banks", "usb-c-cables", "mini-pcs", "kvm-switches", "usb-c-docks", "ssds", "nas", "wireless-chargers", "monitors", "memory", "power-supplies", "cpu-coolers", "graphics-cards", "video-cables", "ethernet-cables", "pc-power-cables", "usb-cables". Example: "chargers".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • changedInput schema / properties / brand / description
      Previous value: -"Brand name, for example Anker or UGREEN."New value: +"Optional. Brand name, matched exactly but ignoring case and spacing. Up to 60 characters. No default (all brands). Example: \"Anker\" or \"UGREEN\"."
    • changedInput schema / properties / category / description
      Previous value: -"Product category: chargers, power-banks, usb-c-cables, mini-pcs, kvm-switches, usb-c-docks, ssds, nas, wireless-chargers, monitors, memory, power-supplies, cpu-coolers, graphics-cards, video-cables, ethernet-cables, pc-power-cables, usb-cables."New value: +"Required. The one product category to search, as a slug. One of: \"chargers\", \"power-banks\", \"usb-c-cables\", \"mini-pcs\", \"kvm-switches\", \"usb-c-docks\", \"ssds\", \"nas\", \"wireless-chargers\", \"monitors\", \"memory\", \"power-supplies\", \"cpu-coolers\", \"graphics-cards\", \"video-cables\", \"ethernet-cables\", \"pc-power-cables\", \"usb-cables\". Example: \"chargers\"."
    • changedInput schema / properties / flags / description
      Previous value: -"Yes/no fields, for example {\"pd31_epr\": true}."New value: +"Optional. Yes/no conditions as an object of {boolean field name: true or false}. Valid names depend on the category and are listed in every response under filterable_fields.yes_no. Example: {\"pd31_epr\": true} for chargers, {\"flight_ok\": true} for power banks."
    • changedInput schema / properties / lang / description
      Previous value: -"Language for text fields: en, zh-hant (Traditional Chinese) or zh-hans (Simplified Chinese)."New value: +"Language of text fields (notes, labels, answers). One of: \"en\" (English), \"zh-hant\" (Traditional Chinese), \"zh-hans\" (Simplified Chinese). Default \"en\". Spec values and model numbers are the same in every language. Example: \"zh-hant\"."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of products to return: a whole number from 1 to 10. Default 10. The response also gives total_matches. Example: 5."
    • changedInput schema / properties / max / description
      Previous value: -"Upper bounds, for example {\"weight_g\": 300}."New value: +"Optional. Maximum values as an object of {numeric field name: number}; a product passes when the field is at most that number. Same field names as min. Products with no value for the field are excluded. Example: {\"weight_g\": 300}."
    • changedInput schema / properties / min / description
      Previous value: -"Lower bounds, for example {\"total_output_w\": 100}."New value: +"Optional. Minimum values as an object of {numeric field name: number}; a product passes when the field is at least that number. Field names end in their unit (_w watts, _g grams, _mm millimetres, _mah, _gbps). Valid names depend on the category and are listed in every response under filterable_fields.numeric. Products with no value for the field are excluded. Example: {\"total_output_w\": 100, \"usb_c_ports\": 2}."
    • addedInput schema / properties / order / description
      Added value: +"Sort direction when sort_by is set: \"asc\" (smallest first) or \"desc\" (largest first). Default \"asc\". Example: \"desc\" with sort_by \"total_output_w\" for the most powerful first."
    • changedInput schema / properties / query / description
      Previous value: -"Words that must appear in the product name or model number."New value: +"Optional. Space-separated words that must all appear in the product name, model number or other model numbers; case is ignored. Up to 120 characters. No default. Example: \"Prime 160W\" or \"A2687\"."
    • changedInput schema / properties / sort_by / description
      Previous value: -"Numeric field to sort by. Without it, the site order is kept."New value: +"Optional. One numeric field name to sort results by (same names as min and max). Products with no value for that field are left out when sorting. No default: without it, results keep the site's own order. Example: \"weight_g\"."
  2. 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 safety, and the description adds substantive behavior: cap of 10, source URL and check date per result, per-category filterable fields in every response, and exclusion of unknown or recalled products. It still omits pagination details and full result shape, but that is minor because annotations and schema carry those concerns.

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?

The definition is front-loaded and compact: purpose and return shape first, then filter mechanics, then exclusions. All five sentences carry relevant information, and nothing is repeated unnecessarily.

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 10-parameter, nested search tool with no output schema, the description covers the key call-time behavior: category scope, filter mechanics, result cap, and exclusions. It could say more about returned product fields or total_matches, but the schema already documents those parameters and the description is sufficient to invoke 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 coverage is 100%, so the baseline is 3; the description summarizes min/max objects and flags but does not add syntax or field-level meaning beyond the schema's detailed parameter descriptions. The note that responses list filterable/sortable fields is useful, but it is behavioral context rather than parameter semantics.

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 uses a specific verb (filters) and resource (verified products) and scopes it to one category and spec values, with a concrete return cap. It is clear enough to distinguish from get_product and compare_products, though it never names a sibling or explicitly contrasts use cases.

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?

It implies usage for spec-based filtering in a single category and explains min/max and flags, but gives no explicit when-to-use rule, no exclusions, and no named alternatives. An agent must infer that this is not for fetching a known product or comparing candidates.

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