Skip to main content
Glama

AINumbers Fintech Intelligence Suite

E-Invoice VAT Calculation Verifier

verify_einvoice_vat_calc
Read-onlyIdempotent

E-Invoice VAT Calculation Verifier: OpenChainGraph compute node (compliance_mandate). Deterministic OpenChainGraph compute node. By default (compute:"auto") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:"browser" forces client-side execution and returns a browser delegation URL instead. gpu:true nodes always delegate to the browser. Inputs are processed transiently to compute the response and are not stored, logged, or retained. Use synthetic or anonymised inputs only. Exports an AP2 artifact with execution_hash for chain provenance. Consumes upstream artifacts from: art-293-einvoice-format-validator. Output feeds: art-295-einvoice-jurisdiction-mandate-router. Open at: https://ainumbers.co/chaingraph/art-294-einvoice-vat-calc-verifier.html FV-status (published/proven/still-trusted for this spec): /fv-status/565f2dd45a55e0ff0f8dafde8c1080f9e1484b32a5aaa96f4d7739a236b9258a.json — a snapshot, not a subscription; this receipt verifies offline regardless of whether that file is ever fetched. Summary: Recompute an e-invoice's line VAT, per-category tax subtotals, tax total, and grand total from its line items under a supplied rounding convention, then compare against the document-asserted amounts. Outputs: consistent, grand_total_computed, grand_total_delta, parse_error, rounding, subtotal_deltas, tax_total_computed, tax_total_delta. Output schema: call describe_tool("verify_einvoice_vat_calc").

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "verify_einvoice_vat_calc"
  }
}

Input Schema

NameRequiredDescriptionDefault
computeNoCompute mode (v0.4 Compute Binding). "auto" (default) = server for gpu:false nodes with registered kernels; "server" = force server-side; "browser" = always return browser delegation URL. gpu:true nodes always delegate.
parent_hashesNoexecution_hash values from upstream ChainGraph AP2 artifacts to chain from (sets chain.parent_hashes in the export).
parent_tool_idsNotool_id values matching parent_hashes, in the same order.
policy_parametersNoInput parameters for this tool's decision function. For gpu:false nodes with a registered kernel, these are computed server-side when compute is "auto" or "server". Required: document, rounding. Unknown keys are refused.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed3 schema fields changed
    • changedInput schema / properties / policy_parameters / description
      Previous value: -"Input parameters for this tool's decision function. For gpu:false nodes with a registered kernel, these are computed server-side when compute is \"auto\" or \"server\". See the tool's manifest for field names."New value: +"Input parameters for this tool's decision function. For gpu:false nodes with a registered kernel, these are computed server-side when compute is \"auto\" or \"server\". Required: document, rounding. Unknown keys are refused."
    • addedInput schema / properties / policy_parameters / properties
      Added value: +{
      +  "document": {},
      +  "rounding": {}
      +}
    • removedInput schema / properties / policy_parameters / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "consistent": {
      -      "type": "boolean"
      -    },
      -    "grand_total_computed": {
      -      "type": "integer"
      -    },
      -    "grand_total_delta": {
      -      "type": "integer"
      -    },
      -    "parse_error": {
      -      "type": "string"
      -    },
      -    "rounding": {
      -      "properties": {
      -        "granularity": {
      -          "type": "string"
      -        },
      -        "method": {
      -          "type": "string"
      -        }
      -      },
      -      "type": "object"
      -    },
      -    "subtotal_deltas": {
      -      "items": {
      -        "properties": {
      -          "matched_asserted_subtotal": {
      -            "type": "boolean"
      -          },
      -          "tax_amount_computed": {
      -            "type": "integer"
      -          },
      -          "tax_amount_delta": {
      -            "type": "integer"
      -          },
      -          "taxable_amount_computed": {
      -            "type": "integer"
      -          },
      -          "taxable_amount_delta": {
      -            "type": "integer"
      -          },
      -          "vat_category": {
      -            "type": "string"
      -          },
      -          "vat_rate_pct": {
      -            "type": "integer"
      -          }
      -        },
      -        "type": "object"
      -      },
      -      "type": "array"
      -    },
      -    "tax_total_computed": {
      -      "type": "integer"
      -    },
      -    "tax_total_delta": {
      -      "type": "integer"
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "consistent": {
      +      "type": "boolean"
      +    },
      +    "grand_total_computed": {
      +      "type": "integer"
      +    },
      +    "grand_total_delta": {
      +      "type": "integer"
      +    },
      +    "parse_error": {
      +      "type": "string"
      +    },
      +    "rounding": {
      +      "properties": {
      +        "granularity": {
      +          "type": "string"
      +        },
      +        "method": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "subtotal_deltas": {
      +      "items": {
      +        "properties": {
      +          "matched_asserted_subtotal": {
      +            "type": "boolean"
      +          },
      +          "tax_amount_computed": {
      +            "type": "integer"
      +          },
      +          "tax_amount_delta": {
      +            "type": "integer"
      +          },
      +          "taxable_amount_computed": {
      +            "type": "integer"
      +          },
      +          "taxable_amount_delta": {
      +            "type": "integer"
      +          },
      +          "vat_category": {
      +            "type": "string"
      +          },
      +          "vat_rate_pct": {
      +            "type": "integer"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "tax_total_computed": {
      +      "type": "integer"
      +    },
      +    "tax_total_delta": {
      +      "type": "integer"
      +    }
      +  },
      +  "type": "object"
      +}
  5. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered; the description still adds real value by disclosing that inputs are processed transiently with no storage or logging, that only synthetic/anonymised inputs should be used, that an AP2 artifact with execution_hash is exported, and that compute:'browser' or gpu:true returns a delegation URL instead. These are genuine behavioral traits not captured by annotations. It does not describe the shape or content of the exported artifact, which keeps it below 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is badly front-loaded: it opens with a title restatement, repeats the compute-mode semantics already in the schema, and intersperses long URLs and a 64-hex FV-status receipt path before the actual purpose appears in 'Summary'. Several sentences duplicate structured fields rather than earning their place, though the individual sentences are grammatical.

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?

With no output schema, the description does list the returned fields (consistent, grand_total_computed, deltas, rounding, parse_error), and it covers privacy, provenance and chain position, which is a lot for a compute node. However, it leaves the structure of policy_parameters.document undefined and only gestures at output field semantics, and the closing 'call describe_tool(...)' defers rather than explains.

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%, so the baseline is 3, and much of the description's compute-mode passage simply restates the 'compute' enum description verbatim. The only added meaning is the mention of a supplied rounding convention and a document with asserted amounts, which maps to the two required policy_parameters keys; the internal structure of those nested objects is left undocumented in both places.

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 'Summary' sentence names a specific verb and resource chain: recompute line VAT, per-category subtotals, tax total and grand total from line items under a supplied rounding convention, then compare to document-asserted amounts. That is clearly distinguishable from siblings like validate_einvoice_format and route_einvoice_jurisdiction_mandate. It loses a point because the statement of purpose is buried at the end behind title restatement and generic compute-node boilerplate.

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?

Usage is only implied through the chain position: it consumes art-293-einvoice-format-validator output and feeds art-295-einvoice-jurisdiction-mandate-router, which tells an agent roughly when in a pipeline it belongs. There is no explicit when-to-use or when-not, and no comparison against close siblings such as validate_einvoice_format or validate_vida_einvoice_conformance.

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.