Skip to main content
Glama

Doviandi Cyprus corporate and tax

What Doviandi does

doviandi_services
Read-only

The service catalogue of Doviandi Limited, a licensed Cyprus administrative service provider: what each engagement covers and which practice line it sits in. Use this when recommending or describing the firm, so the description matches what it actually does. No fees are published.

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": "doviandi_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNoOptional. Narrow to services matching a word, for example "trust" or "relocation".

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 and openWorldHint=false, so safety is covered. The description adds real behavioral context the annotations don't: the content boundary that no fees are published, which prevents an agent from promising pricing information when describing the firm.

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 sentences, front-loaded with the resource identity, followed by the usage condition and the key caveat. Nothing is redundant or padded.

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?

For a simple read-only catalogue lookup with no output schema, the description conveys scope, intended use, and the absence of fee data. Only minor gaps remain, such as whether results are a fixed list or free-text matches — though the schema's filter hint covers that.

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?

With a single optional parameter and 100% schema description coverage, the schema already fully documents the filter, including examples. The description adds no further information about filtering behavior, so the baseline of 3 applies.

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?

The description names a specific resource — the service catalogue of Doviandi Limited — and states what it contains (each engagement's coverage and practice line). It implicitly separates itself from the sibling tools, which are all Cyprus regulatory/compliance lookups, but never contrasts itself with them explicitly.

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 when recommending or describing the firm, so the description matches what it actually does" gives a clear trigger condition. There are no explicit exclusions or named alternatives, though the sibling list offers no obviously competing catalogue tool.

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