Skip to main content
Glama
Sign In

ProofPass

by eu.proofpass
OverviewDiscussionsAdmin

Add a recipient to the distribution list

add_recipient

Adds one address to the distribution list of the connected account, for all products or for the given ones, as "Abnehmer eintragen" does in the dashboard without "jetzt zustellen". No mail is sent; the first delivery is started in the dashboard. Refuses an address that is already on the list. Only add people who are customers of the account holder.

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

Input Schema

NameRequiredDescriptionDefault
nameNoContact person
emailYesE-mail address of the recipient
companyNoCompany
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.
product_idsNoOnly these products; default all products
mail_languageNoISO 639-1 language of the delivery mails: de, en, fr, it, nl, pl, cs, sk, hu, sl, hr, ro, es, pt, da or sv. Default: the language of the manufacturer page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare the write, non-destructive, non-idempotent, closed-world profile. The description adds meaningful behavior beyond them: no mail is dispatched, first delivery is triggered manually in the dashboard, and duplicate addresses are rejected — matching idempotentHint=false. It omits permission/authorization requirements and rate limits.

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 action and the no-mail guarantee, and the duplicate-refusal rule follows logically. The quoted German dashboard labels are useful for mapping but add some verbosity an English-only agent cannot act on.

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?

For a 6-parameter mutation with annotations and no output schema, the definition covers the important behavioral facts (no email, duplicate refusal, product scoping, customer-only policy). It leaves the return value and error behavior implicit, which is a modest gap.

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 the schema already documents all six fields, including enums and defaults; baseline 3 applies. The description only echoes product scoping and adds nothing about name, company or the two language fields.

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 — 'Adds one address to the distribution list of the connected account' — and clarifies the product scope ('for all products or for the given ones'). It implicitly separates itself from listing/preview siblings by stressing 'No mail is sent', but it never names an alternative outright.

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 through domain constraints ('Only add people who are customers of the account holder') and the dashboard analogy, but there is no explicit when-to-use versus when-not, nor any pointer to a sibling such as a preview or list tool before adding.

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