Skip to main content
Glama
iseppo

e-arveldaja MCP Server

by iseppo

Check VAT Registration Threshold

check_vat_registration_threshold
Read-onlyIdempotent

Analyze turnover from confirmed invoices and manual adjustments to determine if a non-VAT-registered Estonian company is approaching or exceeding the 40,000 EUR VAT registration threshold.

Instructions

Check whether a non-VAT-registered Estonian company may be approaching or exceeding the 40 000 EUR VAT registration threshold under the 2025 rules. Read-only advisory: confirmed sale invoices provide the taxable/0% turnover base, while real-estate, insurance, and financial turnover are supplied separately so the operator can decide whether they are non-incidental and count toward the threshold.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNoCalendar year to check. Defaults to the current year.
financial_turnoverNoEUR turnover from financial services, e.g. non-incidental lending interest, securities/FX activity, leasing or payment services. Counts toward the threshold only when it is business turnover and not incidental; bank deposit interest, received dividends, and incidental investment disposals are normally excluded.
insurance_turnoverNoEUR turnover from insurance/reinsurance/intermediation services. Counts toward the threshold only when not incidental.
manual_bucket_sourceNoWhether the manually entered real_estate/insurance/financial/exempt/incidental buckets are already included in confirmed sale invoices. Defaults to outside_sale_invoices; use included_in_sale_invoices to reclassify parts of sale-invoice turnover and avoid double counting.
real_estate_turnoverNoEUR turnover from KMS §16(2) p 2, 3, 6 real-estate transactions/rent. Counts toward the threshold only when not fixed-asset disposal and not incidental.
exempt_social_turnoverNoEUR social-type exempt turnover such as healthcare or education. Reported separately and not counted toward the 40 000 EUR threshold.
taxable_turnover_adjustmentNoManual EUR adjustment to confirmed sale-invoice turnover. Use negative values to exclude fixed-asset disposals, non-Estonian-place turnover, or other amounts that should not count; use positive values for taxable/0% turnover not represented by sale invoices.
incidental_excluded_turnoverNoEUR real-estate/financial/insurance turnover the operator has judged incidental. Reported separately and not counted toward the threshold.
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds behavioral context: it relies on confirmed sale invoices and requires separate inputs for real estate, insurance, and financial turnover, with operator judgment on incidental status. This goes beyond annotations and is consistent with them.

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?

Two sentences: first defines the core purpose, second elaborates on turnover components. Every sentence adds value, though a bit more structure (e.g., listing turnover types) could improve scannability. No wasted words.

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?

The description covers the core logic (turnover composition, operator decision on incidental items) well. No output schema exists, but the tool's advisory nature and parameter descriptions compensate. It lacks details on return format, but the purpose is clear enough for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds meaning by explaining that financial, insurance, real estate, and exempt social turnover are supplied separately for operator judgment, and that adjustments can exclude certain amounts. This enriches parameter understanding beyond raw schema descriptions.

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?

Description clearly states the tool checks whether a non-VAT-registered Estonian company may exceed the 40,000 EUR threshold under 2025 rules. It specifies the exact threshold amount, jurisdiction, and year, making the purpose highly specific and distinguishable from sibling tools like get_vat_info.

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 implies usage for advisory threshold checking and mentions read-only nature, but does not explicitly exclude scenarios or compare to alternatives. It clearly states the context (non-VAT-registered Estonian company, 2025 rules), which helps an agent decide when to invoke it.

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/iseppo/e-arveldaja-mcp'

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