Skip to main content
Glama
Sign In

ProofPass

by eu.proofpass
OverviewDiscussionsAdmin

List a manufacturer’s products and current documents

list_manufacturer_documents
Read-onlyIdempotent

Lists the public products of one checked manufacturer with their current documents (kind, language, version, revision date, PDF URL), 25 per page. / Listet die Produkte eines Herstellers mit ihren aktuellen Dokumenten.

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": {
      "manufacturer": "<manufacturer>"
    },
    "name": "list_manufacturer_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage, 25 products each. Default 1
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.
manufacturerYesManufacturer slug, the part after /hersteller/ in the address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds that only 'public' products are returned, what fields come back, and that pages hold 25 products; it does not cover behavior for an unknown slug or an empty document set.

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 core sentence is front-loaded and dense with useful detail, with zero filler. The immediate German restatement is redundant for most readers and slightly dilutes conciseness, though it is short.

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 takes on the burden of describing returns, and it does so by naming kind, language, version, revision date and PDF URL, plus pagination size. It is largely complete for a small read-only list tool, missing only edge-case behavior and pagination bounds handling.

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 all three parameters are already documented, including the default page size and the language enum. The description only reinforces the page size ('25 per page') and adds no semantics for 'language' or slug format beyond the schema, so the baseline 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 description gives a specific verb and resource ('Lists the public products of one checked manufacturer with their current documents') and even enumerates the document fields returned plus the page size. It does not explicitly distinguish itself from near-siblings such as list_my_products or search_products, so it stops short of a 5.

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 rather than stated: an agent can infer this is the browse-by-manufacturer path, and the schema clarifies that 'manufacturer' is the URL slug. There is no explicit when-to-use/when-not guidance and no mention that a slug may need to be obtained via find_manufacturer first.

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