Skip to main content
Glama
Sign In

VAT.SUPPORT

by io.github.vmalyshev1
OverviewDiscussionsAdmin

intrastat_threshold_check

Evaluate statutory Intrastat reporting obligations for cross-border physical goods movement (dispatches and arrivals) across all 27 EU Member States and Northern Ireland.

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": {
      "business_country": "<business_country>"
    },
    "name": "intrastat_threshold_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoResponse language: en, ru, es, zh-CN
arrivals_unsureNoSet to true if arrival volume is unknown
business_countryYesTwo-letter ISO country code of establishment (e.g. DE, FR, PL, IT, ES)
dispatches_unsureNoSet to true if dispatch volume is unknown
annual_arrivals_eurNoTotal annual value of goods received from other EU Member States in EUR
business_subdivisionNoOptional regional overlay (pass 'NI' for Northern Ireland)
annual_dispatches_eurNoTotal annual value of goods shipped to other EU Member States in EUR

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses jurisdictional coverage (27 EU states plus Northern Ireland) but says nothing about whether the result is advisory or binding, what the response contains, or how the unsure flags change behavior — significant gaps for a compliance-evaluation tool.

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?

A single front-loaded sentence with no wasted wording; the scope qualifier follows the purpose statement naturally. It could be slightly richer without losing efficiency, but nothing needs trimming.

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 seven parameters, no annotations, and no output schema, the definition should say more about the return shape and how unsure-volume inputs are handled. Jurisdictional scope is well covered, but an agent cannot fully predict the response from this sentence alone.

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 unsure flags, language, and subdivision overlay is already documented. The description adds the jurisdictional scope but no extra meaning about parameter interplay, so the baseline of 3 applies.

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 description gives a specific verb ('Evaluate') and resource ('statutory Intrastat reporting obligations') plus the exact scope of the data covered (dispatches and arrivals, all 27 EU Member States and Northern Ireland). This clearly separates it from the VAT-oriented siblings, though it does not name any sibling explicitly.

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?

The use case is implied by 'evaluate statutory reporting obligations,' but there is no explicit statement of when to call this versus something like vat_compliance_full, no prerequisites, and no guidance on using the *_unsure flags when volumes are unknown.

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

All VAT.SUPPORT toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources