mcp-server

Plan Global Setup — Entrepreneur Blueprint

plan_global_setup

Read-only

Composed planner giving one origin-aware answer to the FULL global-setup question — mobility (residence/citizenship options via the Freedom Compass), tax-residence pairing, entity stack by customer market, holding layer, banking access and protection/succession pointers, each layer from Mirabello-verified, provenance-carrying data. Use for questions like: I am an Egyptian founder selling SaaS to the US — what is my full setup? Pass from_citizenship (ISO alpha-2 array) and any of: from_tax_residence, markets (array of us|eu|ch|asia|mea — where the CUSTOMERS are), archetype (solo-lean = freelancer/solo to ~1M; scaleup = 1-10M with team; enterprise = 10M+ multi-region), budget_usd (mobility budget), include_mobility (default true). Rule zero: profit tax follows the OWNER (residence/PoEM/CFC), not the customers. Information only, never advice; ends in a consultation route for real-fit users.

Input Schema

TableJSON Schema

Name	Required	Description
`markets`	No	customer markets: us \| eu \| ch \| asia \| mea
`archetype`	No	solo-lean \| scaleup \| enterprise
`budget_usd`	No	mobility/investment budget for the residence-citizenship layer
`from_citizenship`	No	current citizenship(s), ISO alpha-2
`include_mobility`	No	include the Freedom Compass mobility layer (default true)
`from_tax_residence`	No	current tax residence, ISO alpha-2

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present only when the request could not be fulfilled.
`terms`	No	Acceptable-use and information-not-advice terms.
`source`	No	Attribution for the data, when it is not Mirabello Consultancy itself.
`book_url`	No	Link to request a consultation with a Mirabello specialist, for a personal case.
`provider`	No	Always "Mirabello Consultancy".
`disclaimer`	No	Information, not legal/tax/financial/immigration advice; figures indicative.
`data_updated`	No	Date the underlying dataset was last updated.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 8, 2026

removedOutput schema / properties / book_a_consultation

Removed value: -{
-  "description": "URL to book a Mirabello consultation.",
-  "type": "string"
-}

addedOutput schema / properties / book_url

Added value: +{
+  "description": "Link to request a consultation with a Mirabello specialist, for a personal case.",
+  "type": "string"
+}

changedOutput schema / properties / source / description

Previous value: -"Attribution for the data."New value: +"Attribution for the data, when it is not Mirabello Consultancy itself."

Changed1 schema field changedJul 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Mirabello response envelope. Tool-specific fields vary; the provenance/disclaimer envelope is always present.",
+  "properties": {
+    "book_a_consultation": {
+      "description": "URL to book a Mirabello consultation.",
+      "type": "string"
+    },
+    "data_updated": {
+      "description": "Date the underlying dataset was last updated.",
+      "type": "string"
+    },
+    "disclaimer": {
+      "description": "Information, not legal/tax/financial/immigration advice; figures indicative.",
+      "type": "string"
+    },
+    "error": {
+      "description": "Present only when the request could not be fulfilled.",
+      "type": "string"
+    },
+    "provider": {
+      "description": "Always \"Mirabello Consultancy\".",
+      "type": "string"
+    },
+    "source": {
+      "description": "Attribution for the data.",
+      "type": "string"
+    },
+    "terms": {
+      "description": "Acceptable-use and information-not-advice terms.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedJul 25, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already establish it as a safe, read-only, non-open-world call, and the description adds real behavioral context beyond them: data is 'Mirabello-verified, provenance-carrying,' output is 'information only, never advice,' and it 'ends in a consultation route for real-fit users.' The 'rule zero' note further discloses the planner's underlying logic.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded, but the body collapses a large amount of guidance into one dense, run-on paragraph. The archetype definitions and markets clarification earn their place, but the packing makes it harder to scan than a structured breakdown would.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter planner with rich annotations and an output schema, the description covers purpose, triggering context, every input's semantics, data provenance, and the disclaimer/consultation funnel. An agent has everything needed to select and invoke it correctly, and return values are covered by the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description genuinely adds meaning: it clarifies markets means where the CUSTOMERS are (not the owner), defines archetype bands (solo-lean ~1M, scaleup 1-10M, enterprise 10M+), and notes include_mobility defaults to true. That is value the schema text alone does not carry.

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 verb+resource — a 'composed planner' that answers the FULL global-setup question across mobility, tax-residence, entity stack, holding layer, banking and succession. It clearly distinguishes itself from the many single-domain siblings (get_banking_access, get_mobility_optionality, find_low_tax) by being the aggregate, origin-aware answer.

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?

Gives a concrete triggering example ('I am an Egyptian founder selling SaaS to the US — what is my full setup?') and enumerates exactly which inputs to pass, including the meaning of archetype and markets. It stops short of stating when NOT to use it (e.g. for a single-layer question, use the dedicated sibling), so it's clear on when-to-use but not on exclusions.

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

All mcp-server 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.