Skip to main content
Glama

vat_triangulation_audit

Read-onlyIdempotent

[EU cross-border triangular transaction auditor. Statutory audit, read-only, side-effect free]. Audits simplified triangular trade transactions under Article 141 of Council Directive 2006/112/EC involving three distinct Member States, generating mandatory invoice notations, verifying VAT shift to final customer (Art. 197), and determining Intrastat obligations. Usage: Use this tool when Company B buys goods from Company A and sells to Company C with direct transport from A to C. Returns: JSON object with { isArticle141SimplificationEligible: boolean, memberStatesInvolved: object, mandatoryInvoiceStatementPartyBToC: string, vatLiabilityTransferredToPartyC: boolean, partyB_VatRegistrationInCountryCRequired: boolean, intrastatReportingGuidelines: object }.

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": {
      "partyA_Supplier": "<partyA_Supplier>",
      "partyB_Intermediary": "<partyB_Intermediary>",
      "partyC_FinalCustomer": "<partyC_FinalCustomer>",
      "goodsShippedDirectlyFromAToC": "<goodsShippedDirectlyFromAToC>",
      "netTransactionAmountEur": "<netTransactionAmountEur>"
    },
    "name": "vat_triangulation_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
invoiceLanguageNoLanguage for the statutory invoice notation (default: EN)
partyA_SupplierYesParty A: Original seller / manufacturer
partyB_IntermediaryYesParty B: Promoter / intermediary buyer-reseller
partyC_FinalCustomerYesParty C: Final recipient in destination country
netTransactionAmountEurYesTotal net transaction amount in EUR
goodsShippedDirectlyFromAToCYesTrue if physical transport of goods occurred directly from Member State A to Member State C without entering Country B

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description reinforces them with 'statutory audit, read-only, side-effect free' plus the legal basis, so the agent knows nothing is mutated. It also discloses the return payload key-by-key, which matters because there is no output schema. Minor redundancy with the annotations keeps it from a 5.

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?

Three sentences in a clear bracket-tag / Usage / Returns structure, front-loaded with the legal basis and scope. The bracketed qualifier and the explicit Returns block each carry information the schema does not, so nothing is wasted.

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 six-parameter, nested-object tool with no output schema, the description is nearly complete: it names the legal regime, the triggering scenario, and all returned fields. It omits error/failure behavior for ineligible transactions (e.g. what the response looks like when isArticle141SimplificationEligible is false), which is the only meaningful gap.

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 every parameter including the nested party objects and the invoiceLanguage enum is already documented. The description adds only the A/B/C role framing implied by the usage sentence; it gives no extra constraint such as whether distinct Member State country codes are validated or what happens if A and C share a country. Baseline 3 is appropriate.

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 — auditing simplified triangular trade transactions under Article 141 of Directive 2006/112/EC — and enumerates the concrete outputs (invoice notation, Art. 197 VAT shift, Intrastat obligations). An agent can distinguish this from the many unrelated compliance tools in the catalog without opening 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 'Usage' line gives an explicit triggering condition: B buys from A and sells to C with direct transport A→C. That is a clear selection rule. It stops short of exclusions (e.g. non-EU parties, more than three parties, or goods routed through B), so it does not reach a 5.

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