Skip to main content
Glama
mahdi-salmanzade

MCP-Dubai

by mahdi-salmanzade
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

visa_recommend

Read-onlyIdempotent

Recommend the right UAE visa type based on a founder or employee profile, including income, employer, trade license, and residency duration.

Instructions

Recommend a UAE visa type for a given founder/employee profile.

Input Schema

NameRequiredDescriptionDefault
ageNoAge in years (used for retirement visa).
profileYesOne of: founder, salaried_employee, freelancer, remote_worker, investor, real_estate_investor, specialized_talent, spouse_or_dependent, retiree, tourist.
has_uae_employerNoTrue if there is a UAE-registered employer.
annual_income_aedNoAnnual income in AED for freelancer profiles.
duration_years_minNoOptional minimum residency duration.
monthly_salary_aedNoMonthly salary in AED for preliminary screening.
has_uae_trade_licenseNoTrue if the user already holds a UAE trade license.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.1
    • changedInput schema / properties / monthly_salary_aed / description
      Previous value: -"Monthly basic salary in AED, if relevant."New value: +"Monthly salary in AED for preliminary screening."
  2. First observedv0.4.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds no behavioral context beyond that, such as whether the recommendation is advisory only, what factors influence the output, or any limitations. With annotations covering the safety profile, a 3 is the minimum viable score.

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?

The description is a single front-loaded sentence with no wasted words. It is appropriately sized for a simple recommendation tool.

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?

The description covers the basic purpose and required input, and an output schema exists so return values need not be explained. However, it omits guidance on when to use this tool instead of sibling visa tools, leaving a gap in an environment with many related tools.

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 the input schema already documents all seven parameters thoroughly. The description only mentions 'profile' and does not add extra meaning or constraints beyond what the schema provides. Baseline of 3 applies when the schema does the heavy lifting.

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 states a specific verb and resource: 'Recommend a UAE visa type' for a founder/employee profile. It clearly identifies the tool's purpose without being tautological. However, it does not explicitly distinguish itself from sibling tools like list_visa_types, visa_details, or golden_visa_check.

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 or when-not-to-use guidance and does not mention alternatives. It only states the input context ('for a given founder/employee profile'), leaving the agent to infer when this tool is preferred over related visa tools.

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

Deploy Server

Other Tools