REGULARUS

Verify a safety report

verify_report

Check a signed REGULARUS safety report by the verification number printed below the signature and in the footer (16 characters, e.g. K7Q2-9XMV-3HPD-RW4T, also as QR code). Returns product and version as in the report, signing date, assessor with qualification, status (valid, superseded by a newer version, or withdrawn) and the SHA-256 hash of the PDF file. A number that is not found means the report does not come from REGULARUS. The sample number MUSTER returns an example.

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

Input Schema

Name	Required	Description	Default
`lang`	No	Language of the verification page link (default de).
`number`	Yes	Verification number from the report, with or without hyphens.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 14, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden and mostly delivers: it enumerates the returned fields (product, version, signing date, assessor, status, SHA-256 hash), defines the three status values, and states the not-found semantics. It does not mention read-only safety, rate limits, or whether lookups are logged, but the substantive outcomes are disclosed.

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-loads the purpose, then location/format, then return values, then the edge case and sample. Dense but every clause carries information; the parenthetical format example is a little long but justified for input correctness.

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?

There is no output schema, so the description must enumerate returns, and it does so fully, including status semantics and the not-found case. An agent has everything needed to call the tool and interpret the result.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: the number's origin on the report, its 16-character hyphenated format, QR-code availability, and the MUSTER sample value. The lang parameter is left to the schema, which documents it adequately.

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: 'Check a signed REGULARUS safety report'. It is unambiguous against siblings get_fixed_price and list_documents, which are unrelated retrieval tools, and the description leaves no doubt about what is being verified.

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?

Explains exactly where the verification number comes from (below the signature, in the footer, as a QR code), its 16-character format, and the critical exclusion rule that an unfound number means the report is not from REGULARUS. There is no real alternative tool to route to, so the absence of explicit 'use X instead' guidance is minor.

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

All REGULARUS 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?