Skip to main content
Glama

Doviandi Cyprus corporate and tax

Test whether a review may replace a full audit

cyprus_audit_or_review_test
Read-only

Apply article 152A of the Companies Law Cap. 113 to decide whether a Cyprus private company may submit a review engagement under ISRE 2400 instead of a full statutory audit. There is no audit exemption in Cyprus; this tests a substitution.

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": {
      "net_turnover": "<net_turnover>",
      "gross_assets": "<gross_assets>"
    },
    "name": "cyprus_audit_or_review_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
gross_assetsYesTotal value of assets without deducting liabilities.
net_turnoverYesNet turnover including rental, interest, dividend and royalty income.
group_exceeds_limits_on_aggregateNoTrue if the group exceeds the turnover or asset thresholds measured on aggregate rather than company by company.
prepares_or_is_in_consolidated_accountsNoTrue if the company prepares consolidated financial statements, or is itself included in another company’s. Either one removes the relief whatever the size.
within_limits_for_two_consecutive_yearsNoTrue if net turnover and gross assets were both under the thresholds in each of two consecutive financial years. One year on its own is not enough.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / group_exceeds_limits_on_aggregate / description
      Added value: +"True if the group exceeds the turnover or asset thresholds measured on aggregate rather than company by company."
    • addedInput schema / properties / prepares_or_is_in_consolidated_accounts / description
      Added value: +"True if the company prepares consolidated financial statements, or is itself included in another company’s. Either one removes the relief whatever the size."
    • addedInput schema / properties / within_limits_for_two_consecutive_years / description
      Added value: +"True if net turnover and gross assets were both under the thresholds in each of two consecutive financial years. One year on its own is not enough."
  2. First observed

TDQS

A3.8/5.0
Behavior3/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 and the description need not repeat it. The description adds real domain context — no audit exemption exists, so this only tests substitution — but says nothing about the form of the result (a boolean determination? a reasoned answer?), and there is no output schema to fill that gap.

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 tight sentences with the operative rule and the scoping caveat front-loaded. Nothing is redundant and every clause carries information the agent needs.

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?

With no output schema, the description should ideally indicate what a caller receives back, and it only implies a yes/no determination. Otherwise it is complete for a read-only, fully documented five-parameter decision tool: purpose, legal basis, and the no-exemption caveat are all present.

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 all five parameters, including the two-year and consolidation caveats, are already fully documented in the schema. The description mentions thresholds only in passing and adds no format, units, or edge-case guidance beyond what the property descriptions provide, so the baseline 3 applies.

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 legal mechanism (article 152A, Companies Law Cap. 113) and the exact decision it produces: whether a Cyprus private company may file an ISRE 2400 review instead of a statutory audit. This is clearly distinguishable from the sibling tests (tax residency, VAT registration, 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage (a size/consolidation based substitution test) and adds the useful framing that 'there is no audit exemption in Cyprus; this tests a substitution,' which steers the agent away from misusing it as an exemption check. However, it never says when to call this versus cyprus_compliance_obligations or the other test tools, and gives no prerequisites beyond the implied company context.

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