Skip to main content
Glama

Search certified products

search_products
Read-onlyIdempotent

Find products that hold a third-party certification NonToxicFinder has checked against the certifier's registry or the maker's page. Only products with a current, recently read certification are returned. An empty list means no certified match in this data, not that none exists. Link people to the url given in each result and never construct a retailer link. Say "last read on " for a certification. Say "brand-level" when evidence_scope is "brand". Ratings are scores, not certifications.

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
marksNoCertification mark keys (see list_marks). A product needs at least one of them as a certification.
queryNoWhat the person is looking for, for example "baby shampoo".
categoryNoA category key. A parent key also matches its child categories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: results are restricted to current, recently read certifications, and an empty result carries a specific meaning. The remaining sentences are response-presentation rules (link to the returned url, never build a retailer link, say 'last read on <date>', say 'brand-level' when evidence_scope is 'brand') rather than tool behavior, which is helpful but a different category.

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?

Purpose and the key caveat about empty results are front-loaded, then the output-presentation rules follow compactly. Every sentence carries a distinct instruction with no repetition, and the presentation rules have to live here because there is no output schema.

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?

With no output schema, the description steps in to explain that each result carries a url, that evidence_scope can be brand-level, and that ratings are scores rather than certifications, which prevents the most likely misreporting. Combined with annotations covering the safety profile, an agent has what it needs to call and report correctly; only pagination/ordering behavior is left unspecified.

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 75%, so the schema largely documents limit, query, marks and category, including the parent-matches-child category rule and the at-least-one-mark requirement. The description adds no parameter-level detail of its own; its only field references (evidence_scope, url, ratings) are output fields, not inputs, so the baseline of 3 applies.

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 first sentence gives a specific verb and resource (find products) plus a precise scope: only products with a third-party certification verified against the certifier registry or maker page. That is far more than a restatement of the name. It stops short of naming how it differs from get_product or list_marks, so it is clear but not sibling-differentiating.

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 query/category/marks parameters and the note that an empty list means no certified match in this data rather than no match anywhere, which is useful interpretation guidance. There is no explicit when-to-use or when-to-use-something-else statement, and neither get_product nor list_marks is mentioned as an alternative path.

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