Skip to main content
Glama

Mirabello Immigration Intelligence

Find Charity Jurisdictions

find_charity_jurisdictions
Read-onlyIdempotent

Find jurisdictions for setting up a CHARITABLE/PHILANTHROPIC structure — charitable foundations (e.g. the Liechtenstein gemeinnützige Stiftung), donor-advised funds (US 501(c)(3) ecosystem), charitable trusts, waqf — with donor tax relief, the entity tax status, cross-border granting and the standout vehicle. The philanthropy/legacy complement to the residence/citizenship + tax + trust layers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_charity_jurisdictions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results returned (default 20, up to 200). The list is ranked; total_matched gives the full count.
vehicleNoe.g. foundation, donor-advised fund, charitable trust, waqf
donor_reliefNoonly jurisdictions giving donors a tax deduction/credit

Output Schema

NameRequiredDescriptionDefault
errorNo
termsNo
sourceNo
book_urlNo
providerNo
disclaimerNo
data_updatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Maximum results returned (default 20, up to 200). The list is ranked; total_matched gives the full count.",
      +  "examples": [
      +    20
      +  ],
      +  "maximum": 200,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • changedOutput schema / description
      Previous value: -"Mirabello response envelope. Tool-specific fields vary; the provenance/disclaimer envelope is always present."New value: +"Mirabello envelope; tool fields vary; error only on failure."
    • removedOutput schema / properties / book_url / description
      Removed value: -"Link to request a consultation with a Mirabello specialist, for a personal case."
    • removedOutput schema / properties / data_updated / description
      Removed value: -"Date the underlying dataset was last updated."
    • removedOutput schema / properties / disclaimer / description
      Removed value: -"Information, not legal/tax/financial/immigration advice; figures indicative."
    • removedOutput schema / properties / error / description
      Removed value: -"Present only when the request could not be fulfilled."
    • removedOutput schema / properties / provider / description
      Removed value: -"Always \"Mirabello Consultancy\"."
    • removedOutput schema / properties / source / description
      Removed value: -"Attribution for the data, when it is not Mirabello Consultancy itself."
    • removedOutput schema / properties / terms / description
      Removed value: -"Acceptable-use and information-not-advice terms."
  2. 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."
  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

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuine value beyond that by naming the comparison dimensions returned for each jurisdiction — donor tax relief, entity tax status, cross-border granting, standout vehicle — which tells the agent what the results are good for.

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?

Two sentences, front-loaded with the core scope and specific examples. The second sentence is somewhat dense with positioning language but earns its place by establishing the tool's role in the wider layering.

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, complete parameter documentation and full annotations, the description only needs to frame scope and results, which it does. Minor gap: no hint about ranking criteria or how best to use the ranked order, though the limit parameter covers pagination.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so limit, vehicle and donor_relief are already fully documented including default, cap, and ranking behavior. The description echoes the vehicle taxonomy and 'donor tax relief' but adds no filtering nuance (e.g. matching semantics for vehicle strings) beyond the schema.

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 ('find jurisdictions') scoped precisely to charitable/philanthropic structures, and enumerates the vehicle classes covered (gemeinnützige Stiftung, US 501(c)(3) DAFs, charitable trusts, waqf). This clearly separates it from the sibling find_formation_jurisdictions and find_trust_jurisdictions without needing to name them.

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?

The charitable/philanthropic framing plus the closing line ('complement to the residence/citizenship + tax + trust layers') tells an agent when this tool applies and where it sits relative to adjacent tools. It stops short of explicit exclusions or a named alternative ('for non-charitable vehicles use find_trust_jurisdictions').

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.