Skip to main content
Glama

Search products

search_products
Read-onlyIdempotent

Searches the Verateca register by product name, brand, ingredient or barcode. Returns up to 10 matches with IDs, brands, page addresses and recent published prices where available. Use detail "full" for the number of offers and more record details. Results are ordered by match, never by payment. Reference data only: it does not cover medication interactions, diagnosis or treatment decisions.

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
limitNoNumber of results, 1–10.
queryYesProduct name, brand, ingredient or barcode (UPC/EAN).
detailNoCompact answer by default. Use full for the complete published record.compact
countryNoThe United States is the only market currently available.US

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, openWorldHint=false and destructiveHint=false, so safety is covered. The description still adds real behavioral context: the 10-result ceiling, the fields returned, and notably that ranking is 'by match, never by payment' – a non-obvious trust property. It stops short of describing truncation behavior when the query matches more than 10 records or what an empty result looks like.

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?

Five short sentences, each doing distinct work: purpose, return shape, the full-detail switch, ranking policy, and scope limits. The purpose and scope are front-loaded and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 carries the burden of explaining return values and does so (IDs, brands, page addresses, prices, offers under full detail). For a read-only four-parameter search tool, nothing an agent needs to invoke it correctly is missing.

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 all four parameters are already documented, which sets the baseline at 3. The description adds some meaning beyond the schema by tying detail='full' to the number of offers and richer record fields, and by implying the effective cap on results, but it does not explain query syntax or barcode formats beyond what the schema says.

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 opens with a specific verb and resource: 'Searches the Verateca register by product name, brand, ingredient or barcode', and states what comes back (up to 10 matches with IDs, brands, page addresses, recent published prices). It separates itself from a single-record lookup by describing multi-field querying, though it never names get_product or get_ingredient as the route for a known item.

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?

It gives an explicit exclusion ('does not cover medication interactions, diagnosis or treatment decisions') and in-line guidance to switch to detail 'full' when offers and full record details are needed. What is missing is routing to the sibling tools for single-record or comparison work, so the agent must infer when to leave search_products.

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