Skip to main content
Glama

Doviandi Cyprus corporate and tax

Calculate the charge for filing or paying Cyprus tax late

cyprus_late_filing_charge
Read-only

Apply article 50A of the Assessment and Collection of Taxes Law N.4/1978 to a late filing or late payment and return the charge. Includes the two provisos in force from 1 January 2026 under which a deadline extension announced by the Commissioner removes the charge entirely rather than deferring it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cyprus_late_filing_charge"
  }
}

Input Schema

NameRequiredDescriptionDefault
tax_dueNoTax unpaid at the deadline, for the payment charge.
taxpayerNoWho is late. The charge differs between the two. Defaults to company.company
months_payment_lateNoWhole months between the due date and payment. A further charge applies once two months pass.
tax_paid_at_submissionNoThe tax shown on the return was paid when the return was submitted.
turnover_or_assets_over_1mNoCompanies above one million euro of turnover or assets carry the higher charge.
filed_within_announced_extensionNoFiled inside a deadline the Commissioner announced publicly.
after_a_formal_notice_from_the_commissionerNoA notice allowing not less than 60 days was served and not complied with.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / months_payment_late / description
      Added value: +"Whole months between the due date and payment. A further charge applies once two months pass."
    • addedInput schema / properties / taxpayer / description
      Added value: +"Who is late. The charge differs between the two. Defaults to company."
  2. 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 readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: the two provisos effective 1 January 2026 mean an announced extension eliminates the charge rather than deferring it, which materially changes how an agent should interpret the result.

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?

Two tightly written sentences with the legal basis and the returned value front-loaded, followed by the one caveat that changes the answer. Nothing is redundant with the name or schema.

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 7-parameter, zero-required calculator with no output schema, the description omits the structure of the calculation: it never indicates that tax_due and months_payment_late feed the payment charge while tax_paid_at_submission drives the filing charge, nor what the returned value looks like (amount, breakdown, both charges). Adequate but with clear gaps.

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 is already documented in the schema, including the taxpayer enum and the proviso flags. The description adds no additional semantics about parameter interactions or which inputs are needed for the filing charge versus the payment charge; baseline 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?

States a specific verb ('apply article 50A ... and return the charge') on a specific resource (late filing or late payment charge). The scope is narrow enough that it is clearly distinguishable from sibling lookup/test tools such as cyprus_fact_lookup or cyprus_compliance_obligations.

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 makes clear this is the tool for computing a late filing/late payment charge under the Cyprus statute, which is a clear usage context. It does not name an alternative tool or state when not to use it, so it stops short of a 5.

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