Skip to main content
Glama
Sign In

ProofPass

by eu.proofpass
OverviewDiscussionsAdmin

Find a manufacturer page

find_manufacturer
Read-onlyIdempotent

Finds checked manufacturers on ProofPass by name and returns the address of their public page and their slug (for list_manufacturer_documents and search_products). Only manufacturers that are checked, not paused and have at least one current document.

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

Input Schema

NameRequiredDescriptionDefault
nameYesManufacturer or brand name, or part of it, e.g. "Muster"
limitNoAt most this many results, 1 to 20. Default 10
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.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, but the description adds genuine behavioral context the annotations cannot: results are restricted to manufacturers that are checked, not paused, and have at least one current document. That tells the agent why a known manufacturer might be absent. It does not describe zero-result behavior or ordering.

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?

Two sentences, no filler. The action and return values come first, then the eligibility constraint, then the downstream-use hint — a well front-loaded order for an agent scanning the definition.

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 correctly compensates by naming the two returned fields, and it discloses the eligibility filter. Remaining minor gaps are pagination/limit behavior and what an empty result looks like, neither of which blocks a correct call.

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%, so name, limit and language are already fully documented in the schema, including the enum values and the default. The description only restates 'by name' and adds no format or interpretation detail beyond that, so the baseline of 3 applies.

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?

Names a specific verb and resource ('Finds checked manufacturers on ProofPass by name') and goes further to state what is returned: the public page address and the slug. It also ties the slug to the two sibling tools that consume it, so the agent can place the tool in a workflow 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The parenthetical '(for list_manufacturer_documents and search_products)' makes the intended downstream use explicit, which is strong context. It stops short of stating when NOT to use it or naming an alternative lookup path, so it falls short of full when/when-not guidance.

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