mcp-server

Plan Global Setup — Entrepreneur Blueprint

plan_global_setup

Read-only

THE COMPOSED TOOL: one origin-aware answer for 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.
`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.
`book_a_consultation`	No	URL to book a Mirabello consultation.

Schema Changelog

Changes observed during successful MCP inspections.

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 declare readOnlyHint=true and destructiveHint=false. The description adds useful behavioral context beyond that: it is 'information only, never advice', uses Mirabello-verified provenance-carrying data, and ends in a consultation route. No contradiction with the annotations.

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 description is dense and substantively valuable, but it is one long ALL-CAPS-heavy run-on block that mixes purpose, parameter guide, tax principle, and consultation routing. The content earns its place, but the structure is harder to scan than it should be; bullet-like separation would help.

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 complex 6-parameter composed tool, the description covers the trigger question, parameter semantics, the governing tax rule, data provenance, and the post-answer consultation handoff. Since an output schema exists, the description does not need to explain return values. No material gap remains.

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 the baseline is 3. The description adds real business semantics: markets means where the CUSTOMERS are, archetype is mapped to revenue/team ranges, budget_usd is scoped to mobility, and include_mobility's default is stated. This goes beyond the bare schema descriptions.

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?

The description clearly identifies this as the composed/aggregate tool that answers the FULL global-setup question, enumerating the layers it covers: mobility, tax-residence pairing, entity stack, holding layer, banking, and protection/succession. This distinguishes it from the many single-layer get_* and find_* siblings. The concrete example question further anchors the resource.

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?

Provides an explicit trigger ('Use for questions like: I am an Egyptian founder selling SaaS to the US') and specifies which parameters to pass. It does not name alternatives or state when not to use it, but the composed-tool framing and the example make the selection clear.

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.