Skip to main content
Glama

Find products

search_products
Read-onlyIdempotent

Find products by name, e.g. "Pillow Talk", "Shape Tape", "Hoola". Returns ids and names to use with get_product and compare_products.

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
limitNoMax results (default 10)
queryYesProduct name or part of it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/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 the safety profile is fully covered by structured data. The description's added value is disclosing the return payload (ids and names), which matters because there is no output schema. It stops short of stating whether matching is exact or partial, whether results are ranked, or how the default limit interacts with truncation.

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?

Two short sentences with no filler: purpose and examples first, downstream usage second. Every clause earns its place, and the most decision-relevant information (what it searches and what it returns) is front-loaded.

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 simple two-parameter read-only lookup with a fully described schema and complete safety annotations, the definition covers what the tool does, what it returns, and where the results feed next. The only meaningful gap is the absence of any note on match semantics or result ordering, which an agent would need to interpret a multi-result response.

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%, with both query and limit documented in the schema, so the baseline is 3. The quoted example names illustrate the expected query form and hint at partial-name matching, but they add little beyond the schema's own "Product name or part of it" phrasing, and the description says nothing about the limit parameter or its maximum of 25.

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 ("Find products") plus concrete example queries ("Pillow Talk", "Shape Tape", "Hoola") that make the name-lookup scope unambiguous. It also distinguishes itself from get_product and compare_products by positioning itself as the upstream id-resolver, though it doesn't distinguish itself from name-search-adjacent siblings like trending or best_in_category.

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?

The second sentence gives real workflow guidance: use this to obtain ids for get_product and compare_products, which is exactly the when-to-use information an agent needs for the downstream path. However, there is no exclusion guidance — nothing says to prefer trending or best_in_category when the agent has no product name in hand, so the agent must infer that a name query is required.

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