Skip to main content
Glama
Sign In
rechnungsapi-mcp

rechnungsapi-mcp

Official
by Rechnungsapi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Validate ZUGFeRD PDF

validate_zugferd_pdf

Validate the embedded XML in ZUGFeRD PDFs and optionally cross-check it against the visual PDF.

Instructions

Validate a ZUGFeRD PDF's embedded XML content.

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

Input Schema

NameRequiredDescriptionDefault
zugferdFile64YesBase64-encoded ZUGFeRD PDF
comparePDF2XMLNoAlso cross-check the embedded XML against the visual PDF content

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It narrows validation to the embedded XML (useful scoping), but says nothing about what is checked, whether the PDF/A conformance or visual content is validated, what a failure returns, or whether external services/files are required.

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?

A single tight sentence with the key scope qualifier (embedded XML) front-loaded; no filler. It is arguably under-specified rather than over-long, but structurally clean.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description must explain the validation outcome and error semantics, and it does neither. Given a sibling validate_xrechnung_xml and a family of ZUGFeRD tools, an agent also lacks the differentiation needed to pick correctly.

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%, with both zugferdFile64 and comparePDF2XML documented in the schema, so the baseline is 3. The description adds no meaning beyond the schema, and notably never mentions the comparePDF2XML cross-check option.

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 (validate) and a specific resource (a ZUGFeRD PDF's embedded XML content), which is meaningfully narrower than validating the PDF as a whole. It does not, however, distinguish itself from the sibling validate_xrechnung_xml or explain how it relates to create_zugferd_from_pdf / extract_xrechnung_from_zugferd.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no statement of when to reach for this tool versus validate_xrechnung_xml (a sibling validation tool) or the various create/extract siblings. The agent must infer usage purely from the name and the format label.

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

Deploy Server

Other Tools