ProofPass

Create a product that is not public

create_product_draft

Creates a product in the connected account that is not shown publicly and holds no documents, as "Neues Produkt" with "Nicht öffentlich zeigen" does in the dashboard. Refuses with the reason when the account holds no more products. Returns the id, the QR link and the dashboard link where documents are uploaded and the product is made public.

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": "create_product_draft"
  }
}

Input Schema

Name	Required	Description
`ufi`	No	UFI, e.g. N1Q0-30DW-K00N-4VKE
`gtin`	No	GTIN/EAN with 8, 12, 13 or 14 digits
`name`	Yes	Product name as it should appear
`keywords`	No	Search words, comma separated: old names, colours, pack sizes
`language`	No	Language 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.
`description`	No	Two or three sentences on what the product is for
`article_number`	No	Article number

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the visibility state of the result, that no documents are attached, a quota failure mode ("Refuses with the reason when the account holds no more products"), and the returned handles (id, QR link, dashboard link) — none of which the annotations convey.

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 sentences, front-loaded with the creation action and then the failure mode and return values. Slightly clunky in the translated dashboard-reference clause, but every sentence carries distinct information.

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?

With no output schema, the description compensates by naming what the call returns and the main failure condition, and the non-public/no-documents state is the key caveat an agent needs. Nothing material is missing for a single-required-parameter create 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 coverage is 100%, so every parameter including ufi, gtin, keywords and language is already described in the schema. The description adds no extra semantics about required versus optional fields or how values are validated, 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?

States a specific verb and resource ("Creates a product in the connected account") and pins down the exact state of the created object (not publicly visible, no documents), so an agent can distinguish it from update_product or list_my_products without opening a 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?

The dashboard analogy ("as 'Neues Produkt' with 'Nicht öffentlich zeigen' does") implies the intended context, but there is no explicit when-to-use or when-not-to-use statement and no named alternative such as update_product for existing items.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ProofPass tools Inspect

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

Need Help?