Skip to main content
Glama

mcp-server

by io.github.mirabello-consultancy
OverviewDiscussionsAdmin

Find Formation Jurisdictions

find_formation_jurisdictions
Read-only

FILTER the Mirabello formation profiles to find company/structure jurisdictions matching constraints: remote_only (fully remote formation), max_setup_usd (setup cost ceiling), banking_tier (good|moderate — minimum), eu_clean (exclude EU Annex I/II and FATF-listed), lane (company|trust). Each match returns key, vehicle, tier, status, headline tax line, cost ranges, timeline, banking tier and ideal-client line, with the full honest per-jurisdiction profile available on request. Rule zero: profit tax follows the OWNER (residence/PoEM/CFC), not the entity. Information, not advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
laneNocompany | trust
eu_cleanNoTrue to require the jurisdiction be absent from EU tax and AML listings.
remote_onlyNoTrue to return only options that can be completed without travelling to the country.
banking_tierNogood | moderate (minimum acceptable)
max_setup_usdNoMaximum acceptable set-up cost in USD.

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. Changed4 schema fields changed
    • addedInput schema / properties / eu_clean / description
      Added value: +"True to require the jurisdiction be absent from EU tax and AML listings."
    • addedInput schema / properties / max_setup_usd / description
      Added value: +"Maximum acceptable set-up cost in USD."
    • addedInput schema / properties / max_setup_usd / examples
      Added value: +[
+  25000
+]
    • addedInput schema / properties / remote_only / description
      Added value: +"True to return only options that can be completed without travelling to the country."
  3. 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"
+}
  4. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, covering the safety profile, so the bar is lower. The description adds useful non-schema context: results are 'honest' summary profiles with the full profile 'on request', and an explicit 'Information, not advice' disclaimer, plus the 'Rule zero' PoEM/CFC caveat.

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?

The action is front-loaded ('FILTER...'), and the output enumeration stays tight. The trailing 'Rule zero' and advice-disclaimer sentences are somewhat tangential but short and add domain value, so nothing is egregiously wasteful.

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?

An output schema exists, so return details are not strictly required, yet the description still outlines the match fields. With annotations, full schema coverage, and an output schema present, the definition is complete enough, though it lacks explicit sibling routing.

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 adds meaning beyond the schema: banking_tier is explicitly a 'minimum', and eu_clean is spelled out as 'exclude EU Annex I/II and FATF-listed'. It also ties each parameter name to its effect in the filter.

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 (FILTER) plus resource (Mirabello formation profiles for company/structure jurisdictions) and enumerates what a match returns. An agent can distinguish it from find_trust_jurisdictions, find_low_tax, and compare_formation without opening the schema.

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?

The filter semantics (remote_only, eu_clean, banking_tier, lane) imply when the tool is useful, but there is no explicit when-to-use/when-not guidance and no named alternatives despite overlap with siblings like find_trust_jurisdictions and find_low_tax. Usage must be inferred.

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