Skip to main content
Glama

Doviandi Cyprus corporate and tax

Book a scoping call with Doviandi

request_scoping_call

Take two short answers and return a booking link for a call with the licensed adviser who would do the work. Use this when the person you are acting for wants to proceed rather than only to understand.

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": {
      "what_are_you_trying_to_do": "<what_are_you_trying_to_do>"
    },
    "name": "request_scoping_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
where_are_you_nowNoOptional. Country of residence, or where the business currently sits.
what_are_you_trying_to_doYesThe objective, or the problem being hit. One or two sentences.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-idempotent, non-destructive, closed-world. The description adds that the output is a booking link tied to a licensed adviser, which is useful, but it doesn't say what the 'two short answers' actually trigger (lead capture? email sent?), whether repeat calls create duplicate bookings, or what happens after the link is handed over. Given readOnlyHint=false, that side-effect gap matters.

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 with no filler, and the outcome (booking link) is front-loaded before the usage condition. Nothing is repeated from the title 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?

No output schema exists, and the description covers the return shape only at a high level ('a booking link'). For a non-read-only tool in a set otherwise made of pure lookups, it should clarify whether submitting the answers records anything about the user or initiates contact from the adviser. Adequate but leaves a meaningful behavioral unknown.

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 coverage is 100%, so both parameters are already documented with their optionality and intent. The phrase 'two short answers' loosely reinforces the brevity expectation but adds no format or content constraints beyond the schema. Baseline 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 gives a specific action and output: it takes two short answers and returns a booking link for a call with the licensed adviser who would do the work. That is unambiguous, though it doesn't differentiate itself by name from any of the informational siblings (cyprus_fact_lookup, doviandi_services, etc.).

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?

It states the qualifying condition well: use it when the person wants to proceed rather than only to understand. That implicitly excludes the lookup/test siblings, but no alternative tool is named for the 'only understand' case, so the routing is inferred rather than explicit.

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