Skip to main content
Glama

vida_cross_border_digital_reporter

Read-onlyIdempotent

[EU ViDA real-time digital reporting & reverse charge auditor. Pure calculation, read-only, side-effect free]. Audits cross-border B2B intra-community transactions under the EU VAT in the Digital Age (ViDA) Directive, verifying the mandatory 2-business-day issuance window, central VIES transmission requirements, and MTIC carousel fraud risk. Usage: Use this tool to ensure intra-community supplies and cross-border services comply with upcoming EU DRR mandates. Returns: JSON object with { invoiceNumber: string, isVidaCompliant: boolean, digitalReportingWindowHours: number, issuanceDeadlineCompliant: boolean, reportingMechanism: string, vatExemptionBasis: string, buyerVatReverseChargeMandate: boolean, mticCarouselFraudRisk: string }.

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>",
      "taxableEventDateIso": "<taxableEventDateIso>",
      "invoiceIssueDateIso": "<invoiceIssueDateIso>",
      "supplierCountryCode": "<supplierCountryCode>",
      "supplierVatNumber": "<supplierVatNumber>",
      "customerCountryCode": "<customerCountryCode>",
      "customerVatNumber": "<customerVatNumber>",
      "netTaxableAmountEur": "<netTaxableAmountEur>",
      "transactionType": "<transactionType>"
    },
    "name": "vida_cross_border_digital_reporter"
  }
}

Input Schema

NameRequiredDescriptionDefault
invoiceNumberYesInvoice reference number
transactionTypeYesViDA transaction category
customerVatNumberYesStatutory VAT number of customer
supplierVatNumberYesStatutory VAT number of supplier
customerCountryCodeYes2-letter ISO country code of customer (e.g. DE)
invoiceIssueDateIsoYesDate invoice was issued (YYYY-MM-DD)
netTaxableAmountEurYesNet transaction value in EUR
supplierCountryCodeYes2-letter ISO country code of supplier (e.g. IT)
taxableEventDateIsoYesDate goods were shipped or service completed (YYYY-MM-DD)
centralViesSyncTimestampIsoNoOptional timestamp of immediate VIES real-time registry check

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so 'pure calculation, read-only, side-effect free' largely restates them. What the description adds beyond the annotations is substantive: the specific rules being evaluated (issuance window, VIES transmission, MTIC risk) and, in the absence of an output schema, the exact JSON keys returned, including the compliance boolean and the fraud-risk string.

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?

Front-loaded with the core purpose, then usage, then a return-value listing that earns its space because no output schema exists. The bracketed preamble and the restated purity claims are mildly redundant given the annotations, but nothing is padded beyond that.

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

Completeness4/5

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

For a 10-parameter, 9-required audit tool with no output schema, the definition covers what it checks and what it returns, which is most of what an agent needs. It is silent on how the optional centralViesSyncTimestampIso changes the result and on how DOMESTIC_REVERSE_CHARGE is treated relative to the intra-community cases.

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 coverage is 100%, so each of the 10 fields is already documented, which sets the baseline at 3. The description's mention of a mandatory 2-business-day issuance window does add interpretive meaning for the pair taxableEventDateIso/invoiceIssueDateIso and for centralViesSyncTimestampIso, but it never explains how those fields are evaluated or what the window is measured from.

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: audits cross-border B2B intra-community transactions under the EU ViDA Directive, and names the three concrete checks it performs (2-business-day issuance window, central VIES transmission, MTIC carousel fraud risk). The scope is narrow and unmistakable against the listed siblings, none of which do VAT digital reporting.

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 'Usage:' line gives a clear triggering condition: use it to check that intra-community supplies and cross-border services comply with EU DRR mandates. It does not state when NOT to use it or name an alternative for adjacent cases (e.g. domestic-only VAT or non-EU exports), but the transactionType enum implicitly bounds the input domain.

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