Skip to main content
Glama

Doviandi Cyprus corporate and tax

Calculate the Cyprus IP Box nexus fraction and effective rate

cyprus_ip_box_nexus
Read-only

Compute the nexus fraction with the 30 percent uplift, the 80 percent deduction and the resulting effective corporate tax rate on qualifying profit.

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": {
      "qualifying_expenditure": "<qualifying_expenditure>",
      "overall_expenditure": "<overall_expenditure>"
    },
    "name": "cyprus_ip_box_nexus"
  }
}

Input Schema

NameRequiredDescriptionDefault
qualifying_profitNoOptional. Profit attributable to the qualifying asset.
overall_expenditureYesAll expenditure on the asset, including acquisition cost and related party outsourcing.
qualifying_expenditureYesResearch and development carried out by the company itself or outsourced to unrelated parties.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 safety is covered. The description adds the statutory components being applied, which is useful context, but it does not disclose the return payload (no output schema exists) or how the optional qualifying_profit affects results.

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?

A single dense sentence with the computation and its components front-loaded; nothing is wasted or repeated.

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 no output schema, the description must convey return values; it names the nexus fraction and effective rate but omits the formula shape, rounding, and whether the fraction is capped at 1, and it is silent on the behavior when the optional qualifying_profit is omitted.

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 three parameters are already documented in the schema. The description only hints at the role of qualifying profit as the base for the effective rate, adding little beyond structured data — baseline 3.

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?

States a specific verb ('compute') and specific resources (nexus fraction, effective corporate tax rate) along with the statutory building blocks (30% uplift, 80% deduction). It is clearly a calculator, distinguishing it from the lookup/test siblings, though it never names those alternatives.

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?

Usage is implied by the Cyprus IP box regime context and the required expenditure inputs, but there is no explicit statement of when to use this versus e.g. a lookup or the audit/review test, and no prerequisites or exclusions are given.

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