Skip to main content
Glama

Rulepass e-invoicing

Check invoice data

check_invoice
Read-onlyIdempotent

Checks invoice data against the Peppol / EN 16931 business rules without producing XML: returns ready=true, or the list of problems to fix. Same input as create_einvoice.

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>",
      "issueDate": "<issueDate>",
      "seller": "<seller>",
      "buyer": "<buyer>",
      "lines": "<lines>"
    },
    "name": "check_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
bicNo
ibanNo
noteNo
buyerYes
linesYes
formatNopeppol
numberYes
sellerYes
docTypeNoinvoice
dueDateNoInvoices only. Give dueDate or paymentTerms.
currencyNoEUR
issueDateYes
adjustmentsNoDocument-level discounts (allowance) and surcharges (charge), each with the VAT rate it applies to.
deliveryDateNoDate of supply of goods or services, if different from the issue date.
paymentTermsNo
buyerReferenceNo
orderReferenceNo
exemptionReasonNoRequired when a line uses category E.
paymentReferenceNo
precedingInvoiceNoCredit notes: number of the invoice being corrected.
precedingInvoiceDateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world scope, so the safety profile is covered. The description adds genuine behavioral value: it names the rule set enforced and tells the agent the response is either ready=true or a list of problems to fix, which is more than the annotations provide. It stops short of describing the problem-list structure or how exhaustive the rule coverage is.

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 tight sentences with the validation scope front-loaded and the create_einvoice comparison second. Zero wasted wording and the most decision-relevant fact (no XML output) is stated early.

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

Completeness3/5

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

For a complex 21-parameter validation tool with no output schema, the description covers what is checked and the shape of the response at a high level. However, it does not explain the return payload's problem-list format or clarify that the shared input must still satisfy Peppol constraints, leaving gaps against the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 24% across 21 parameters, so the description must compensate and largely does not. 'Same input as create_einvoice' is a useful cross-reference but leaves most fields (e.g. docType, adjustments, payment terms, exemptionReason) undocumented in the description itself. Only the schema's own sparse descriptions carry parameter meaning.

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 ('Checks invoice data'), names the standards it validates against (Peppol / EN 16931), and explicitly distinguishes itself from create_einvoice by noting it produces no XML. An agent can tell this is a validation-only tool without inspecting 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 phrase 'without producing XML' and 'Same input as create_einvoice' clearly route the agent: use this to validate, use create_einvoice to emit XML. It does not state an explicit when-not condition or say whether validation is a prerequisite, but the context is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.