Skip to main content
Glama

mcp-server

by io.github.mirabello-consultancy
OverviewDiscussionsAdmin

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
NameRequiredDescriptionDefault
structureNoprofile key, e.g. us-llc-wy, ae-freezone, sg-pte (omit for the catalogue)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent only when the request could not be fulfilled.
termsNoAcceptable-use and information-not-advice terms.
sourceNoAttribution for the data, when it is not Mirabello Consultancy itself.
book_urlNoLink to request a consultation with a Mirabello specialist, for a personal case.
providerNoAlways "Mirabello Consultancy".
disclaimerNoInformation, not legal/tax/financial/immigration advice; figures indicative.
data_updatedNoDate the underlying dataset was last updated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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."
  2. Changed1 schema field changed
    • 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"
+}
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish a safe, closed-world read (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds genuine context beyond that: the profile's contents (honest tax caveats, cost ranges, substance requirements), that it states who it does NOT fit, and the 'general information, not advice; execution via licensed local partners' disclaimer.

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?

Purpose is front-loaded in the opening clause before the dense key list and the attribute inventory. The 30-key parenthetical is heavy but functionally necessary given the missing enum; a few phrases ('required licensed executor', 'and provenance') could be trimmed without loss.

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 an output schema present, return values need no explanation, and the description covers what the profile contains, the catalogue fallback, and an advisory disclaimer. It stops short of noting provenance/freshness behaviour that siblings like get_provenance and get_recent_changes imply, a minor gap.

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 the param is documented, so baseline would be 3. The description earns above baseline by enumerating the 30 actual valid key values — the schema has no enum, so this list is the only place an agent can learn admissible values, plus it restates the omit-for-catalogue behaviour.

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 and resource ('FULL formation profile for one structure from the Mirabello Global Structuring roster'), enumerates all 30 valid keys, and distinguishes the single-profile retrieval from the catalogue fallback. An agent can tell exactly what comes back and which structure keys are legal.

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?

It says 'Pass structure (the profile key); omit for the catalogue of available keys', which gives usage context for the one parameter. But it never names or excludes the obvious siblings (compare_formation, get_structuring_roster, get_structuring_playbook), so an agent still has to guess this tool's position among 60+ neighbours.

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

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