Skip to main content
Glama
josemvelez78

mcp-europe-business

suggest_vat_treatment

Read-onlyIdempotent

Determine VAT treatment for cross-border EU transactions including reverse charge, OSS/IOSS, and zero-rating based on seller and buyer details.

Instructions

Suggests the likely VAT treatment for a transaction based on seller country, buyer country, buyer VAT registration status, and goods/services type — covering standard VAT, reverse charge, OSS/IOSS, and zero-rating scenarios under EU VAT rules. Returns { treatment, description, seller_charges_vat, applicable_rate, notes, disclaimer }. Use when building checkout VAT logic, invoice generation, or cross-border EU compliance workflows. For digital services sold to EU consumers, OSS is indicated automatically. Always verify with a tax advisor for real transactions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seller_countryYesSeller's country ISO code. Example: 'PT'
buyer_countryYesBuyer's country ISO code. Example: 'DE'
buyer_is_vat_registeredYesWhether the buyer is VAT registered (B2B) or not (B2C)
goods_typeYesType of supply

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
treatmentYes
descriptionYes
seller_charges_vatYes
applicable_rateYes
seller_countryYes
buyer_countryYes
buyer_is_vat_registeredYes
goods_typeYes
notesYes
disclaimerYes

Implementation Reference

  • index.js:930-941 (registration)
    Registration of the 'suggest_vat_treatment' tool with input/output schemas and annotations.
    // ── 27. Suggest VAT Treatment ──
    server.registerTool("suggest_vat_treatment", {
      description: "Suggests the likely VAT treatment for a transaction based on seller country, buyer country, buyer VAT registration status, and goods/services type — covering standard VAT, reverse charge, OSS/IOSS, and zero-rating scenarios under EU VAT rules. Returns { treatment, description, seller_charges_vat, applicable_rate, notes, disclaimer }. Use when building checkout VAT logic, invoice generation, or cross-border EU compliance workflows. For digital services sold to EU consumers, OSS is indicated automatically. Always verify with a tax advisor for real transactions.",
      inputSchema: {
        seller_country: z.string().describe("Seller's country ISO code. Example: 'PT'"),
        buyer_country: z.string().describe("Buyer's country ISO code. Example: 'DE'"),
        buyer_is_vat_registered: z.boolean().describe("Whether the buyer is VAT registered (B2B) or not (B2C)"),
        goods_type: z.enum(["goods", "digital_services", "services"]).describe("Type of supply")
      },
      outputSchema: { treatment: z.string(), description: z.string(), seller_charges_vat: z.boolean(), applicable_rate: z.string(), seller_country: z.string(), buyer_country: z.string(), buyer_is_vat_registered: z.boolean(), goods_type: z.string(), notes: z.string(), disclaimer: z.string() },
          annotations: { title: "Suggest VAT Treatment", readOnlyHint: true, idempotentHint: true, openWorldHint: false }
    }, async ({ seller_country, buyer_country, buyer_is_vat_registered, goods_type }) => {
  • Handler function implementing the VAT treatment suggestion logic. Evaluates seller/buyer countries, VAT registration status, and goods/services type to determine domestic VAT, reverse charge, OSS, export zero-rating, import, or out-of-EU treatment.
    }, async ({ seller_country, buyer_country, buyer_is_vat_registered, goods_type }) => {
      const seller = seller_country.toUpperCase();
      const buyer = buyer_country.toUpperCase();
      const euCountries = ["AT","BE","BG","HR","CY","CZ","DK","EE","FI","FR","DE","GR","HU","IE","IT","LV","LT","LU","MT","NL","PL","PT","RO","SK","SI","ES","SE"];
      const sellerInEU = euCountries.includes(seller);
      const buyerInEU = euCountries.includes(buyer);
    
      let treatment, description, sellerChargesVat, applicableRate, notes;
    
      if (seller === buyer) {
        treatment = "domestic_vat";
        description = "Domestic transaction — standard VAT of seller country applies";
        sellerChargesVat = true;
        applicableRate = "Seller country standard/reduced rate";
        notes = `Apply ${seller} VAT rates. Standard transaction.`;
      } else if (sellerInEU && buyerInEU && buyer_is_vat_registered) {
        treatment = "intra_eu_b2b_reverse_charge";
        description = "Intra-EU B2B supply — reverse charge mechanism applies";
        sellerChargesVat = false;
        applicableRate = "0% (zero-rated at source)";
        notes = `Seller issues zero-rated invoice. Buyer self-accounts for VAT in ${buyer} at local rate. Seller must quote buyer's VAT number on invoice.`;
      } else if (sellerInEU && buyerInEU && !buyer_is_vat_registered) {
        if (goods_type === "digital_services") {
          treatment = "oss_digital_services";
          description = "Intra-EU B2C digital services — OSS (One Stop Shop) scheme";
          sellerChargesVat = true;
          applicableRate = `${buyer} country rate for digital services`;
          notes = `VAT charged at buyer's country rate. Declare and pay via OSS scheme. No need to register in ${buyer} if using OSS.`;
        } else if (goods_type === "goods") {
          treatment = "eu_distance_sales";
          description = "Intra-EU B2C goods — distance selling rules / OSS";
          sellerChargesVat = true;
          applicableRate = `${buyer} country rate (if above €10,000 EU threshold)`;
          notes = `Below €10,000 annual EU B2C threshold: apply seller country VAT. Above threshold: apply buyer country VAT via OSS.`;
        } else {
          treatment = "b2c_services_seller_country";
          description = "Intra-EU B2C services — general rule: seller country VAT";
          sellerChargesVat = true;
          applicableRate = `${seller} country rate`;
          notes = "General rule for B2C services: place of supply is seller's country. Exceptions apply for specific service types (transport, cultural, etc.).";
        }
      } else if (sellerInEU && !buyerInEU) {
        treatment = "export_zero_rated";
        description = "Export outside EU — zero-rated supply";
        sellerChargesVat = false;
        applicableRate = "0% (export)";
        notes = `Supply to ${buyer} outside EU. Zero-rated export. Seller must retain export documentation. ${buyer === "UK" ? "Post-Brexit: UK is treated as third country." : ""}`;
      } else if (!sellerInEU && buyerInEU) {
        treatment = "import_buyer_accounts";
        description = "Import from outside EU — buyer accounts for import VAT";
        sellerChargesVat = false;
        applicableRate = `${buyer} import VAT rate`;
        notes = `Goods/services from outside EU. ${buyer} import VAT applies. For digital services B2C: seller may need to register for IOSS.`;
      } else {
        treatment = "outside_eu_scope";
        description = "Transaction outside EU VAT scope";
        sellerChargesVat = false;
        applicableRate = "N/A";
        notes = "Neither seller nor buyer is in the EU. EU VAT rules do not apply.";
      }
    
      return { content: [{ type: "text", text: JSON.stringify({ treatment, description, seller_charges_vat: sellerChargesVat, applicable_rate: applicableRate, seller_country: seller, buyer_country: buyer, buyer_is_vat_registered, goods_type, notes, disclaimer: "Reference information only — not legal or tax advice. Always verify with a qualified tax advisor for real transactions." }) }] };
    });
Behavior4/5

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

Annotations indicate readOnlyHint=true and idempotentHint=true, and the description aligns with a non-destructive suggestion tool. It adds context about the specific VAT scenarios covered and the returned structure, which complements the annotations without contradiction.

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 concise at about four sentences, front-loaded with the core purpose, followed by return structure, use cases, a specific rule (OSS for digital services), and a disclaimer. Every sentence adds value without redundancy.

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

Completeness5/5

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

Given the complexity of EU VAT rules and the presence of a detailed output schema (implied by the description), the description covers purpose, inputs, outputs, and limitations. It is complete for an AI agent to decide to invoke the tool.

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% with detailed parameter descriptions. The description mentions the parameters (seller country, buyer country, etc.) but does not add significant new meaning beyond what the schema already provides, so the baseline score of 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?

The description clearly states the verb 'suggests', the resource 'VAT treatment', and the scope 'under EU VAT rules', covering specific scenarios like reverse charge, OSS/IOSS. It effectively distinguishes from siblings like 'calculate_vat_amount' which compute amounts rather than treatments.

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 description provides explicit use cases ('Use when building checkout VAT logic, invoice generation, or cross-border EU compliance workflows') and includes a disclaimer to verify with a tax advisor. However, it does not directly mention when not to use or suggest alternative tools, though the sibling context implies differentiation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/josemvelez78/mcp-europe-business'

If you have feedback or need assistance with the MCP directory API, please join our Discord server