Skip to main content
Glama

Doviandi Cyprus corporate and tax

Test whether Cyprus VAT registration is required

cyprus_vat_registration_test
Read-only

Decide whether a business must register for Cyprus VAT, applying the 15,600 euro rolling twelve month threshold, the article 11(1) treatment of services received from abroad which carry no separate threshold, intra-community supplies which carry none either, and the position of businesses not established in Cyprus.

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": {
      "taxable_supplies_last_12_months": "<taxable_supplies_last_12_months>"
    },
    "name": "cyprus_vat_registration_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
established_in_cyprusNoTrue if the business is established in Cyprus. A business not established here has no registration threshold.
makes_intra_community_suppliesNoTrue if the business supplies goods or services to businesses in other EU member states.
taxable_supplies_last_12_monthsYesValue in euro of taxable supplies made in Cyprus over the preceding twelve months. For example 18000.
services_received_from_abroad_last_12_monthsNoValue of services bought from suppliers outside Cyprus in the same period.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / established_in_cyprus / description
      Added value: +"True if the business is established in Cyprus. A business not established here has no registration threshold."
    • addedInput schema / properties / makes_intra_community_supplies / description
      Added value: +"True if the business supplies goods or services to businesses in other EU member states."
    • addedInput schema / properties / taxable_supplies_last_12_months / description
      Added value: +"Value in euro of taxable supplies made in Cyprus over the preceding twelve months. For example 18000."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds real value by disclosing the substantive decision rules and the specific 15,600 euro threshold applied. It does not state the form of the result or whether the outcome is deterministic/binary, which keeps it below 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that leads with the decision and then lists the qualifying rules. It is dense and slightly run-on, but every clause carries substantive legal rule information rather than filler.

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?

For a four-parameter read-only calculator with full schema coverage but no output schema, the description never says what the tool returns (a boolean, a threshold comparison, a reasoned determination). That is the one material gap an agent would want closed before calling it.

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, but the description adds interpretive meaning beyond the schema: it clarifies that services received from abroad and intra-community supplies carry no separate threshold, which directly informs how those two boolean/numeric parameters are weighed. It stops short of mapping each parameter to its role in the calculation.

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 outcome ('Decide whether a business must register for Cyprus VAT') and immediately scopes it to the exact rules applied. It is clearly distinguishable from siblings such as cyprus_tax_residency_test or cyprus_audit_or_review_test, which test different regimes.

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 description implicitly defines coverage by enumerating the scenarios it handles (threshold, article 11(1) services from abroad, intra-community supplies, non-established businesses), which tells an agent the tool is applicable to those cases. However, it never states when NOT to use it or names an alternative sibling, so routing guidance is inferred rather than explicit.

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