Skip to main content
Glama

klergrid-eu-einvoice

generate_sepa_pain001

Generate an ISO 20022 SEPA Credit Transfer payment file (pain.001.001.09 or 001.001.03) with Mod-97 IBAN validation and exact CtrlSum. Charges 1 credit.

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": {
      "messageId": "<messageId>",
      "requestedExecutionDate": "<requestedExecutionDate>",
      "debtor": "<debtor>",
      "transactions": "<transactions>"
    },
    "name": "generate_sepa_pain001"
  }
}

Input Schema

NameRequiredDescriptionDefault
debtorYes
messageIdYes
transactionsYes
schemaVersionNo
requestedExecutionDateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses that the tool validates IBANs with Mod-97, computes an exact CtrlSum, and charges 1 credit, but it does not explain failure behavior, where the generated file is returned or stored, or any permission requirements.

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?

The description is a single, front-loaded sentence with no filler. It efficiently packs the output format, supported versions, validation behavior, CtrlSum guarantee, and credit cost.

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?

This is a complex tool with five parameters, nested objects, zero schema descriptions, and no annotations. The description covers the high-level purpose and cost but omits parameter-level semantics and error behavior, leaving too much for an agent to infer before calling it correctly.

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%, so the description must compensate for undocumented parameters. It only loosely connects to schemaVersion by naming 001.001.09 and 001.001.03, and provides no meaning for messageId, requestedExecutionDate, debtor, or the nested transaction structure.

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 states a specific verb and resource: generate an ISO 20022 SEPA Credit Transfer payment file, with named schema versions and validation behavior. It clearly distinguishes the tool from generic document tools by naming the SEPA pain.001 format, though it does not explicitly contrast itself with sibling tools such as generate_eu_invoice.

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 use case is strongly implied by 'SEPA Credit Transfer payment file,' so an agent can infer this is for creating SEPA payment files. However, the description gives no explicit when-to-use guidance, no prerequisites, and no comparison to alternatives for related payment or invoice generation tasks.

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.

Resources