Skip to main content
Glama
Sign In

ProofPass

by eu.proofpass
OverviewDiscussionsAdmin

Get the current version of a product document

get_current_document
Read-onlyIdempotent

Returns the current published version of one document of a product: title, kind, language, version, revision date, publication date, product page, PDF URL on ProofPass and SHA-256, plus the other languages it exists in. Never an archived version. Kinds: sdb, tdb, dop, dopc, doc, ppwr, manual, epd, cert, other (also "SDS", "TDS", "DoP", "DoC"). / Liefert die aktuelle Fassung eines Dokuments (SDB, TDB, Leistungserklärung …) mit PDF-Link.

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": {
      "product": "<product>",
      "type": "<type>"
    },
    "name": "get_current_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesDocument kind: sdb, tdb, dop, dopc, doc, ppwr, manual, epd, cert, other; "SDS"/"SDB" for the safety data sheet
productYesProduct id from search_products, QR short code, GTIN, "manufacturer-slug/product-slug" or the product page URL
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.
document_languageNoISO 639-1 language of the document, any official EU language, e.g. "de", "en", "pl", "pt", "el". Default: the language of the answer, else the manufacturer’s

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so safety is covered; the description adds useful context that only the current published revision is returned and lists the response contents. It does not say what happens when no current version exists, which is the main remaining behavioral gap.

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?

Front-loaded with the core behavior and the returned-field list, and the scope constraint ('never an archived version') comes early. The trailing German sentence duplicates the English content without adding information.

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 usefully enumerates the returned fields, and the kind vocabulary is spelled out. Missing only the not-found / no-current-revision behavior, which matters for an agent deciding whether to retry or fall back.

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% and the schema already defines type, product, language and document_language in detail. The description's kind list and synonyms (SDS/TDS/DoP/DoC) largely restate the enum, so it adds little beyond the schema — baseline 3.

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?

States a specific verb and resource: returns the current published version of one product document, and enumerates the fields returned (title, kind, version, PDF URL, SHA-256, available languages). An agent can distinguish it from siblings like verify_document or list_manufacturer_documents without opening the schema.

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?

'Never an archived version' implies the boundary against historical/archived lookups, but no alternative tool is named and no explicit when-to-use condition is given. Usage is inferable but not routed.

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