Skip to main content
Glama

Ask Bestie Computers

Find products

search_products
Read-onlyIdempotent

Find products by name, e.g. "9800X3D", "RTX 5070", "Superlight". 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.9/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 upstream. The description adds the return payload (ids and names) and a downstream-consumption hint. With no output schema, it still omits what happens on no match and whether results are ranked or truncated by the limit parameter, so it only modestly exceeds the annotation baseline.

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?

Two short, front-loaded sentences: the purpose and matching examples first, then the return-and-follow-on hint. No filler or restated boilerplate. The nested quotation of example strings is slightly awkward formatting but does not cost clarity.

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 lookup with strong annotations and full schema coverage, this covers what an agent needs to call it and to use its output. Missing only edge behavior such as empty result sets and whether the limit truncates silently, which the absence of an output schema makes mildly more relevant.

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 100%, with query described as "Product name or part of it" and limit bounded 1-25 with a default of 10, so the schema does the heavy lifting and the baseline is 3. The examples reinforce substring/partial-name matching, which is a small but genuine addition. The limit parameter is not addressed in the description at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb plus resource ("Find products by name") with concrete examples ("9800X3D", "RTX 5070", "Superlight") that show the matching granularity. It also states what comes back (ids and names) and names the siblings it feeds into, so an agent can tell it apart from get_product and compare_products without opening a schema.

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?

The description makes the workflow explicit: search here, then pass the returned ids to get_product or compare_products. That is real, actionable context. It stops short of explicit when-not guidance (e.g. what to do on zero results, or when trending/best_in_category is preferable), so it does not reach a 5.

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