Skip to main content
Glama

compatsy home espresso

Search products

search_products
Read-onlyIdempotent

Find products by name or by category and spec filters; returns key specs and the best in-stock offer. Example: {"query":"puck screen","category":"puck_screen","limit":5}

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
limitNo
queryNo
filtersNoNeeds category. Spec field -> exact value, e.g. {"material":"brass"}; an unknown field or value is an error listing the valid ones
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value beyond that by disclosing what comes back ('key specs and the best in-stock offer') even though no output schema exists. It omits any note on result ordering, pagination beyond limit, or behavior when nothing matches, keeping it below 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded clause states the operation and the return, followed by a compact, immediately usable example. No filler or repetition of the schema. The example could be annotated slightly (e.g. what 'limit' does) but nothing is wasted.

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 is the only source of return-value information, and it gives just one clause ('key specs and best in-stock offer') without structure or ranking rules. Combined with 25% schema coverage on four parameters including a nested object, an agent can make a reasonable call but not predict the response shape precisely.

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 only 25% — only the nested 'filters' object is documented — so the description must carry more weight. It does map semantics for three of four parameters (query=name, category=category, filters=spec) and the example clarifies how they combine. The 'limit' parameter is never explained in the description beyond the schema's 1-25 bounds, leaving a partial gap.

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+resource ('Find products') and names the two lookup modes (by name via query, by category/spec filters). It also states the response shape ('key specs and the best in-stock offer'), which tells an agent this is a discovery/listing tool rather than a detail fetch. It does not explicitly contrast itself with siblings like get_product or compare, so it stops short of a 5.

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 implied through the worked example showing query, category and limit together, which demonstrates the intended call pattern. However, there is no statement of when to prefer this over get_product (single-item lookup) or compare, and no exclusions or prerequisites. An agent must infer routing from sibling names alone.

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.