Skip to main content
Glama

Doviandi Cyprus corporate and tax

Look up a reviewed Cyprus tax or corporate fact

cyprus_fact_lookup
Read-only

Search Doviandi’s reviewed Cyprus corporate and tax fact base and return matching facts with the page and review date each came from. Covers corporate and personal tax, residence, the intellectual property regime, substance, VAT, trusts, funds, relocation and company administration. Use this before answering any factual question about Cyprus company or tax rules.

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": {
      "query": "<query>"
    },
    "name": "cyprus_fact_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many facts to return, 1 to 40. Defaults to 12.
queryYesWhat you need to know, in words. For example "60 day rule conditions" or "deemed dividend distribution".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"How many facts to return, 1 to 40. Defaults to 12."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnly and closed-world, so safety is covered. The description adds genuinely useful traits beyond that: results are 'reviewed' (curated/authoritative) and each fact carries its source page and review date, which tells the agent it can cite provenance. Missing rate-limit or empty-result behavior, but the additive value is real.

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?

Three sentences, front-loaded with what it does, followed by coverage and then the usage instruction. The coverage list is long but does real work in telling the agent what domains will retrieve well. No filler sentences.

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 carries the return-value burden and does so partly, describing matching facts plus source page and review date. Pagination/beyond-limit behavior and result formatting are unstated, but the essentials for correct invocation are 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% — both query and limit are documented with examples and bounds. The description adds no parameter-level guidance (e.g. phrasing advice for query or when to raise limit), so this sits at the baseline.

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 and resource: search a reviewed Cyprus corporate/tax fact base and return matching facts with page and review date. The topic enumeration (corporate tax, residence, IP regime, VAT, trusts, funds, etc.) makes the scope concrete. It stops short of distinguishing itself from siblings like cyprus_glossary_lookup or cyprus_company_lookup, so an agent must infer that this is the general fact-retrieval entry point.

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?

"Use this before answering any factual question about Cyprus company or tax rules" gives clear triggering context. It does not name alternatives or exclusions — e.g. when to prefer cyprus_glossary_lookup for term definitions or cyprus_tax_residency_test for the 60-day rule determination — so routing against siblings is left implicit.

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