Moha: hire in the UAE

Prepare a whole account for the person to confirm

prepare_account

Prepares a Moha account without signing in: the company profile, the person setting it up, one to ten hires and colleagues to invite. Returns the quotes and one link: the person opens it, sets a password and the account is created with everything in it. Nothing is charged or sent before that.

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": {
      "company": "<company>",
      "hires": "<hires>"
    },
    "name": "prepare_account"
  }
}

Input Schema

Name	Required	Description
`you`	No	The person setting up the account.
`team`	No	Colleagues to invite when the account is created, each with a role.
`hires`	Yes	The people to hire.
`company`	Yes	The hiring company.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already mark this as a non-destructive write (readOnlyHint=false, destructiveHint=false). The description adds valuable deferred-commit semantics: nothing is charged or sent until the person opens the link and sets a password, and the account is created with everything in it. It does not explain repeated-call behavior, but idempotentHint=false already signals that.

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?

Three sentences with the core action and result front-loaded. It is dense but has no filler; the flow from inputs to returned link is efficient, though a slightly clearer separation of inputs versus returns could improve scanability.

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 complex nested-object tool with no output schema, the description explains the return (quotes and one link) and the deferred creation flow. Combined with 100% schema coverage and annotations, an agent can call it correctly, though error and edge-case behavior is left implicit.

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 all parameter meanings are already documented in the schema. The description adds only a high-level mapping ('company profile', 'the person setting it up', 'one to ten hires and colleagues') and no format or validation details beyond the schema.

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 ('Prepares') and resource ('Moha account'), then enumerates what is included: company profile, the person setting it up, one to ten hires, and colleagues to invite. It is clear what the tool does, but it does not name a sibling such as prepare_hire to differentiate scope.

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?

Implies use when setting up a full account with hires and colleagues, and notes the no-sign-in flow. However, it gives no explicit when-to-use versus prepare_hire, check_prepared_hire, or get_quote, and no exclusions or prerequisites.

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?