mcp-server

Foundation & Trust Rules

get_foundation_rules

Read-only

CHARITABLE & PRIVATE FOUNDATION and TRUST rules for a jurisdiction: whether the foundation legal form exists (Stiftung / fondation / fundación / waqf / foundation company), legal basis, regulator/registry, minimum endowment, governance organs, founder reserved powers, beneficiary rights, charitable-purpose requirements, tax treatment and cross-border donor deductibility, reporting/audit duties, UBO-register visibility, trust recognition (domestic trust law / Hague Convention / not recognised) and lawful foundation+trust combination patterns. Deepens the charity and trust jurisdiction shortlists to 194-country coverage. Pass cc for one jurisdiction; omit for the covered list. Establishment is decided by the competent registry or regulator and executed via licensed local partners; tax outcomes follow the founder's and beneficiaries' residence. Information, not legal or tax advice.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cc`	No	ISO alpha-2 country code, e.g. LI, CH, AE

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."

AddedAug 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds meaningful context: establishment is decided by the competent registry/regulator via licensed local partners, tax outcomes follow founder/beneficiary residence, and the output is information not legal/tax advice. Return format is left to the output 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?

Front-loads the resource and then a dense but purposeful inventory of covered content, followed by usage and a disclaimer. The opening is a long noun phrase rather than a verb-first sentence, and the field list is verbose, but each element supports semantic retrieval.

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?

With an output schema and full annotation coverage, the description is complete: it defines scope, the optional-param behavior, and the advisory limitation. An agent has everything needed to decide whether to call it and with what argument.

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 goes beyond the schema by telling the agent what omitting cc does ('omit for the covered list'), which the bare 'ISO alpha-2 country code' description does not convey.

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 resource (charitable/private foundation and trust rules) and enumerates the exact content returned — legal form existence, regulator, endowment, governance, tax treatment, UBO visibility, trust recognition. The closing line that it 'deepens the charity and trust jurisdiction shortlists to 194-country coverage' distinguishes it from the sibling shortlist tools (find_charity_jurisdictions, find_trust_jurisdictions).

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?

Explicitly says 'Pass cc for one jurisdiction; omit for the covered list,' giving clear context for both invocation modes. It implies a follow-on to the shortlist tools rather than naming an alternative or stating exclusions, so it stops short of a full when/when-not statement.

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.