MCP-Dubai

setup_advisor

Read-onlyIdempotent

Recommends a suitable Dubai jurisdiction and license type for your business, comparing free zones, visas, banks, and tax rules by activity and budget.

Instructions

Recommend the best jurisdiction for setting up a business in Dubai.

Cross-references curated free zones, visas, banks, and tax rules (the headline biz/* feature). Returns a ToolResponse envelope with a structured recommendation: jurisdiction (mainland, an eligible free zone with the applicable DET licence or permit, or offshore), candidate free zones, reasoning, warnings, estimated cost range, timeline, and next steps. Always returns a knowledge block with its latest recorded date, any targeted scope, volatility, verify_at, and disclaimer.

Input Schema

Name	Required	Description	Default
`activity`	Yes	Business activity description (e.g., "SaaS", "consulting", "trading", "ecommerce").
`industry`	No	Industry category. One of: general, saas, tech, ecommerce, consulting, fintech, ai, blockchain, crypto, trading, import_export, manufacturing, logistics, healthcare, media, education, real_estate, fb, retail.	general
`budget_aed`	Yes	Total first-year budget in AED for setup, license, visas, and bank account.
`needs_visa`	No	True if the founder needs a UAE residence visa from this license.
`visa_count`	No	How many visas the company needs in total.
`needs_local_trade`	No	True if the business expects to conduct customer-facing or other licensed activity onshore in Dubai.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.4.1Oct 22, 2026

changedInput schema / properties / needs_local_trade / description

Previous value: -"True if the business needs to invoice mainland\nUAE consumers (B2C) directly without a local distributor."New value: +"True if the business expects to conduct\ncustomer-facing or other licensed activity onshore in Dubai."

First observedv0.4.0Jul 11, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare it read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: the ToolResponse envelope, the specific recommendation fields (jurisdiction, candidates, warnings, cost range, timeline, next steps), and the always-present `knowledge` block with volatility/verify_at/disclaimer metadata.

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?

Purpose is front-loaded in the first sentence, followed by feature scope and a compact return-shape summary. Every sentence carries information; nothing is filler.

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 an output schema present and rich annotations, the description needn't explain return values, yet it still summarizes them usefully and covers the knowledge/verification caveats. The only real gap is the absent routing guidance against near-identical siblings.

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 every parameter is already documented in the schema with defaults and the industry enum spelled out. The description adds no input-parameter meaning of its own, 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?

States a specific verb and resource: 'Recommend the best jurisdiction for setting up a business in Dubai.' It is unmistakably a recommendation/setup tool, but it never differentiates itself from close siblings such as analyze_setup_decision, compare_free_zones, or setup_timeline_estimate, so an agent still has to guess at routing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description gives no when-to-use, when-not, or alternative guidance. It bills itself as 'the headline biz/* feature' but that is promotional rather than a routing rule, leaving the agent to infer whether this supersedes or complements the many other setup-related siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server