Moha: hire in the UAE

Price a hire in the UAE

get_quote

Read-onlyIdempotent

Monthly and upfront cost of employing one person in the UAE through Moha, an Employer of Record: salary split, employer costs, government fees, insurance, our fee and VAT, plus how long the visa takes. No account needed.

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": {
      "monthly_salary_aed": "<monthly_salary_aed>",
      "nationality": "<nationality>"
    },
    "name": "get_quote"
  }
}

Input Schema

Name	Required	Description
`spouse`	No	True if a spouse will move with them on a family visa.
`emirate`	No	Where they will work. Defaults to Dubai.
`children`	No	Children moving with them on family visas.
`insurance`	No	Health insurance plan. Defaults to standard.
`inside_uae`	No	True if the person is already in the UAE. Defaults to false (coming from abroad).
`nationality`	Yes	The employee’s nationality, as a country name. Example: India.
`monthly_salary_aed`	Yes	Total monthly package in AED: basic salary plus allowances. Example: 20000.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the description's added value is the auth disclosure ('No account needed') and the output composition (salary split, employer costs, government fees, insurance, fee, VAT, visa duration). It stops short of telling the agent whether the quote is binding or what units/format the return takes, but it is a solid supplement.

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?

A single front-loaded sentence that leads with the resource and cost breakdown rather than preamble. The clause list is dense but every element (salary split, fees, VAT, visa duration) carries real information; only the 'through Moha, an Employer of Record' aside is slightly 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?

With no output schema, the description usefully enumerates the returned cost components and visa timeframe, which is what an agent needs to know before calling. Minor gaps remain: currency of the totals and whether the estimate is a fixed quote or a variable range.

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% with examples and defaults for every field, so the schema does the heavy lifting. The description adds no meaning about inputs — e.g. it never explains that nationality and salary are the only mandatory drivers, or how spouse/children roll into dependent visa cost.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and computation: 'Monthly and upfront cost of employing one person in the UAE through Moha, an Employer of Record'. The scope (one person, UAE, Moha as EoR) is unambiguous and reads distinctly from action-oriented siblings like prepare_hire or prepare_account.

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

Usage Guidelines3/5

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

Usage is only implied — the agent can infer this is the pricing step that precedes prepare_hire, and 'No account needed' hints it is callable early. There is no explicit when-to-use/when-not statement or named alternative.

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

All Moha: hire in the UAE tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?