Skip to main content
Glama

searchProducts

Search verified-fit kits/filters (USD). Pass shipToCountry when known for soft shipping + approxLocal on the match/card. One match → product island + card. Multiple → choices with id/slug. Then getReviews; quickCheckout to buy.

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": "searchProducts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
deviceModelIdNo
shipToCountryNoISO-2 when known — enables soft ship + approxLocal

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / shipToCountry / description
      Added value: +"ISO-2 when known — enables soft ship + approxLocal"
  2. Changed1 schema field changed
    • addedInput schema / properties / shipToCountry
      Added value: +{
      +  "type": "string"
      +}
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does add real behavioral context about result shaping (one match yields a product island + card, multiple matches yield choices with id/slug) and about the side effect of shipToCountry. It omits pagination/limit behavior, empty-result handling, and any auth or rate-limit notes.

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?

It is compact and front-loads the core action before the follow-up routing. The telegraphic phrasing ('soft ship', 'product island') and chained arrows reduce readability slightly but nothing is padded.

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?

For a 4-parameter tool with no output schema and no annotations, it covers result shape and next-step routing but leaves the meaning of query and deviceModelId, the limit default, and alternative-tool selection unexplained. Adequate but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 25%, so the description must compensate, and it does explain only shipToCountry's effect (soft shipping + approxLocal). The query, limit, and deviceModelId parameters remain undocumented in both schema and description — notably no default or maximum is given for limit, which is just a bare number.

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 gives a specific verb and resource ('Search verified-fit kits/filters (USD)') and conveys domain scope that distinguishes it from generic product lookups. It is somewhat jargon-laden ('verified-fit', 'product island'), but an agent can tell it is a compatibility-scoped product search.

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 gives useful chaining guidance ('Then getReviews; quickCheckout to buy') and a conditional tip ('Pass shipToCountry when known'), but never states when to use this tool instead of the sibling findCompatibleParts or getProduct. The search-versus-lookup distinction is only implied.

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