Skip to main content
Glama
Sign In

ProofPass

by eu.proofpass
OverviewDiscussionsAdmin

Look up a glossary term

get_glossary_term
Read-onlyIdempotent

Looks up one term in ProofPass’s glossary by name or abbreviation (e.g. "UFI", "SDB", "Leistungserklärung", "GPSR") and returns the definition, the explanation, its sources and related terms. The glossary is written in German.

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": {
      "term": "<term>"
    },
    "name": "get_glossary_term"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesTerm or abbreviation
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

A4.5/5.0
Behavior4/5

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

The description provides significant behavioral context beyond the annotations. It specifies the exact types of data returned (definition, explanation, sources, and related terms) and highlights a critical constraint regarding the source language being German, which is vital for retrieval planning.

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?

The description is exceptionally well-structured. It utilizes two concise sentences: the first defines the functionality and input flexibility, and the second provides essential contextual limitations (the language of the glossary). There is zero wasted wording.

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?

The definition is complete for a read-only lookup tool. It covers the resource being queried, the format of input acceptable, and the nature of the data returned (even without an output schema), leaving no significant ambiguity for the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema coverage is 100%, the description adds valuable semantic meaning by providing concrete examples of accepted input formats, such as acronym examples ('UFI') and full German term examples ('Leistungserklärung'). This ensures the agent understands the intended diversity of the 'term' input beyond mere string validation.

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?

The description clearly states the purpose: to look up a term in ProofPass's glossary. It is highly specific, naming the resource (glossary) and the action (lookup by name or abbreviation). This helps distinguish it from general knowledge searches found in sibling tools.

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?

While it does not explicitly state when *not* to use this tool, it establishes clear operational boundaries by defining the resource (ProofPass glossary) it queries. By mentioning specific input examples like 'UFI' or 'GPSR,' it guides the agent on the expected domain of use.

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