Skip to main content
Glama
Sign In

ProofPass

by eu.proofpass
OverviewDiscussionsAdmin

Search ProofPass guides, questions and glossary

search_knowledge
Read-onlyIdempotent

Searches ProofPass’s published guides, questions and glossary (German, English, Polish) and returns title, the short answer, the provision it rests on, the date of the last check and the link. Use for questions on safety data sheets, CLP and UFI, GPSR, construction products, battery and product passport, packaging. When a language has no match, the German library answers and says so.

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_knowledge"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results, default 5
queryYesSearch words, e.g. "Sicherheitsdatenblatt Sprache" or "battery passport"
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.

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 and closed-world, so the safety profile is covered. The description adds genuinely new behavior: the exact response fields (title, short answer, underlying provision, last-check date, link) and the language fallback rule that unmapped languages are answered from the German library with an explicit notice.

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?

Three front-loaded sentences: capability plus return fields first, usage topics second, edge-case fallback last. The topic list is dense but earns its place as a routing cue; the fallback clause mildly duplicates the schema's language documentation.

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 what each result contains, and it covers the cross-language edge case a caller would otherwise be surprised by. It omits any mention of the result cap (limit max 10) or ranking behavior, which is the only notable remaining gap for a search tool.

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 query, limit and language are all documented with examples and defaults, giving a baseline of 3. The description's language-fallback sentence largely restates what the schema's language description already says, adding no new parameter-level syntax or constraints.

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?

States a specific verb and resource ('Searches ProofPass's published guides, questions and glossary') and enumerates the covered content types and languages, so the agent knows exactly what corpus is queried. It does not explicitly distinguish itself from the sibling get_glossary_term, which an agent could plausibly confuse with the glossary portion of this corpus.

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?

Gives concrete when-to-use triggers by topic list: safety data sheets, CLP/UFI, GPSR, construction products, battery and product passport, packaging. There are no exclusions and no named alternatives (e.g. when to prefer get_glossary_term or the check_* tools for a specific compliance question), so routing beyond topic matching is left to inference.

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