mcp-server

Company Formation Profile

get_company_formation

Read-only

FULL formation profile for one structure from the Mirabello Global Structuring roster (30 profiles: ae-freezone, ae-adgm-spv, ae-adgm-foundation, us-llc-wy, sg-pte, hk-ltd, ch-company, ch-holdco, cy-ltd, ie-ltd, mt-trading, hu-kft, ee-ou, je-company, li-structures, lu-soparfi, lu-spf, lu-raif, mu-gbc, bb-ltd, sc-ibc, kn-llc, ky-exempt, ge-structures, my-labuan, kz-aifc, vg-bc, bz-ibc, us-trust-sd, nz-foreign-trust): honest tax position (QFZP/ECI/SUTE-style caveats included), setup/annual cost ranges, timeline, remote feasibility, substance requirements, banking tier, EU/FATF list status, who it genuinely fits AND who it does NOT fit, required licensed executor, and provenance. Pass structure (the profile key); omit for the catalogue of available keys. General information, not advice; execution via licensed local partners.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`structure`	No	profile key, e.g. us-llc-wy, ae-freezone, sg-pte (omit for the catalogue)

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.4/5.0

Behavior4/5

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

Annotations already declare the tool read-only and non-destructive. The description adds meaningful context: the output is general information, not advice, and execution happens via licensed local partners. It also discloses the caveated tax-position content, which sets expectations beyond the schema.

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?

Dense but purposeful, with the core function front-loaded before the profile contents and usage instruction. The long roster list is verbose but useful as a de facto enum; nothing in the description is filler, though the single-paragraph structure could be more scannable.

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 one-optional-parameter, read-only tool with an output schema, the description provides the full accepted key set, the omit-for-catalogue fallback, and a liability caveat. An agent has everything needed to invoke it correctly, and the return shape is already 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% and already documents the optional structure key with examples. The description adds value by enumerating all 30 valid profile keys, materially reducing the risk of an agent passing an invalid or hallucinated structure identifier.

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 that it returns the full formation profile for one structure from a named 30-profile roster and enumerates exactly which structures are covered. This clearly distinguishes it from catalogue-style or comparison siblings by framing it as a single-structure deep dive.

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?

Explains the input contract clearly: pass a structure key for a profile, or omit it for the catalogue of available keys. It gives an agent a concrete selection rule, though it does not explicitly name alternatives like compare_formation or get_structuring_roster.

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.