Skip to main content
Glama
Sign In

ProofPass

by eu.proofpass
OverviewDiscussionsAdmin

Search products with data sheets

search_products
Read-onlyIdempotent

Searches the public products of checked manufacturers on ProofPass by name, article number, GTIN/EAN or UFI, optionally within one manufacturer. Returns up to 20 products with manufacturer, identifiers, available document kinds and the product page URL. / Sucht öffentliche Produkte geprüfter Hersteller nach Name, Artikelnummer, GTIN oder UFI.

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
limitNoAt most this many results, 1 to 20. Default 10
queryYesProduct name, article number, GTIN/EAN or UFI, e.g. "Silikon Neutral" or "9006543210017"
languageNoLanguage of the answer: "de" (German, default), "en" (English) or "pl" (Polish). Product and account answers are written in German and English; content without a translation comes in German.
manufacturerNoManufacturer slug to search within (the part after /hersteller/ in the address)

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: the result cap (up to 20), the fields returned (manufacturer, identifiers, document kinds, product page URL), and the restriction to verified manufacturers' public catalog — useful since no output schema exists.

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?

The English sentence is front-loaded with the verb and packs scope, search keys, result cap, and return fields efficiently. The trailing German sentence is a full duplicate translation, which is defensible for a bilingual service but is redundant payload for an agent reader.

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?

For a read-only search with four fully documented parameters and no output schema, the description covers scope, inputs, result count, and return fields. An agent has everything needed to decide to call it and to interpret the 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 description coverage is 100%, so every parameter — limit, query, language, manufacturer — is already documented with examples and constraints. The description restates the searchable fields and the optional manufacturer scoping but adds no syntax or format detail beyond the schema, making the baseline 3 appropriate.

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?

"Searches the public products of checked manufacturers" gives a specific verb, resource, and scope, and enumerates the searchable identifiers (name, article number, GTIN/EAN, UFI). The "public products of checked manufacturers" qualifier implicitly separates it from list_my_products, but no sibling is named explicitly, so it stops short of full differentiation.

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 by the enumeration of lookup keys — an agent can infer this is the tool for finding a product by identifier or name. However, there is no explicit when-to-use statement, no guidance on when to prefer this over list_my_products or resolve_product, and no stated exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ProofPass toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources