Skip to main content
Glama

FinOps Studio Zero-Auth Bank Validator & 2-Row Taste-Test MCP

preview_eu_einvoice_xml_2_lines

Free 2-line taste-test preview of EN 16931 Peppol BIS 3.0 UBL, German XRechnung 3.0, or Factur-X CII XML invoice generation.

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": {
      "invoiceNumber": "<invoiceNumber>",
      "seller": "<seller>",
      "buyer": "<buyer>",
      "lines": "<lines>"
    },
    "name": "preview_eu_einvoice_xml_2_lines"
  }
}

Input Schema

NameRequiredDescriptionDefault
buyerYes
linesYes
formatNopeppol-ubl-3.0
sellerYes
invoiceNumberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden; it does disclose the key trait that output/sample is capped at two lines and that the preview is free. It says nothing about whether input is validated, what happens if more than two lines are supplied, what errors look like, or what the return value is.

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 front-loaded sentence with no filler; the format options and the 2-line constraint are stated efficiently. It is lean to the point of under-specification, but not wordy.

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?

For a tool with five parameters, deep nested objects, no annotations and no output schema, the description is thin. It omits the shape of the nested objects, what the returned preview looks like (raw XML text vs. a URL), and how the two-line cap is enforced, leaving real gaps for an agent to hit at call time.

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 0% with five parameters including nested objects (seller, buyer, lines). The description only loosely echoes the format enum values and never explains invoiceNumber, the structure of seller/buyer, or the fields required per line, so it does not compensate for the coverage gap.

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?

The description names a specific action (preview of XML invoice generation) plus the concrete standards covered (EN 16931 Peppol BIS 3.0 UBL, XRechnung 3.0, Factur-X CII), which clearly separates it from the sibling preview tools for SEPA, BAI2, DATEV and NACHA. It stops short of explicitly naming those siblings, but the domain is unmistakable.

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?

'taste-test preview' and 'Free 2-line' imply this is a trial run before committing to a full generation, which is useful context. However, no explicit when-to-use/when-not-to-use statement or reference to a full-generation alternative is given, so the guidance is only implied.

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.