Skip to main content
Glama

BRAINIAC Indirect Tax Calculations

EU OSS €10,000 threshold place-of-supply check

indirect-tax_eu-oss-threshold-check
Read-onlyIdempotent

Decide whether an EU-established supplier's B2C cross-border TBE services and distance sales stay taxed at home or switch to the customer's Member State under the EU-wide €10,000 threshold. Price $0.03 USDC. POST /api/v1/indirect-tax/eu-oss-threshold-check. An unpaid call returns the x402 payment terms and does not run.

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": {
      "supplierCountry": "<supplierCountry>",
      "establishedInOtherMemberStates": "<establishedInOtherMemberStates>",
      "previousYearTotalEurCents": "<previousYearTotalEurCents>",
      "sales": "<sales>"
    },
    "name": "indirect-tax_eu-oss-threshold-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
salesYessales, array. Required.
supplierCountryYessupplierCountry, string, length 2 to 2. Required.
optedForDestinationNooptedForDestination, boolean. Required.
previousYearTotalEurCentsYespreviousYearTotalEurCents, integer, from 0 to 9007199254740991. Required.
establishedInOtherMemberStatesYesestablishedInOtherMemberStates, boolean. Required.

Output Schema

NameRequiredDescriptionDefault
perSaleNoperSale. Array.
sourcesNosources. Array.
thresholdNothreshold. Number.
exceededOnNoexceededOn. Object.
limitationsNolimitations. Array.
ossRelevantNoossRelevant. Boolean.
previousYearExceededNopreviousYearExceeded. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds genuinely useful behavior beyond them: the $0.03 USDC cost, the POST endpoint, and the critical fact that an unpaid call returns x402 payment terms and does not execute — an agent needs that to avoid misreading an empty result as a calculation.

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?

Three sentences, front-loaded with the decision, then the commercial/transport metadata, then the payment-gating caveat. Every sentence carries information, though the price-and-endpoint sentence is compressed into a mechanical clause that reads as API metadata rather than guidance.

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?

An output schema exists, so return values need no explanation, and the description covers what the tool decides plus the payment gate. Residual gaps are the meaning of optedForDestination and the required period of the sales array — material for correct invocation but narrowly scoped given how complete the schema is.

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 schema documents each field; the description only implicitly contextualizes previousYearTotalEurCents and the sales array via the €10,000 threshold framing. It says nothing about optedForDestination, which is the OSS election that changes the outcome, or about how supplierCountry/establishedInOtherMemberStates interact with the test.

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 states a precise decision problem: whether an EU-established supplier's B2C cross-border TBE services and distance sales remain taxed at home or shift to the customer's Member State under the €10,000 threshold. The verb ('Decide') and resource (place-of-supply threshold test) are unambiguous, and the scope is narrow enough to separate it from jurisdiction-specific siblings like the Australian or Canadian GST tools.

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?

Context is clear — this applies only to EU-established suppliers making cross-border B2C TBE supplies/distance sales, which implicitly excludes the other jurisdiction tools. However, it never states preconditions (e.g. what period the sales array should cover, or that multi-Member-State establishment overrides the threshold) or any explicit 'do not use when' case.

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