Mirabello Immigration Intelligence

German Emigration Flows by Destination

get_emigration_flows

Read-onlyIdempotent

OFFICIAL GERMAN EMIGRATION DATA: where German citizens actually move, by destination country and year (Destatis statistic 12711-0008, 2016 onwards). Returns departures, arrivals and net migration per destination, plus each destination share of the NAMED-destination base. Revealed preference, not opinion: in 2025 at least 288,579 German citizens deregistered for a move abroad, a net loss of about 96,689; Switzerland, Austria, Spain, the United States and France were the largest stated destinations. CRITICAL, returned in the caveats field: roughly 48% of departures state NO destination, so rankings describe the named base only, and totals are a floor because people leave without deregistering. Never trend across 2015/2016 (definitional break). Popularity is not suitability. Pass year, destination or top. Licence dl-de/by-2-0; Destatis attribution mandatory on reuse.

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": "get_emigration_flows"
  }
}

Input Schema

Name	Required	Description
`top`	No	limit the destination list (default 25)
`year`	No	e.g. "2025"; defaults to the latest available
`destination`	No	destination country name in German, e.g. "Schweiz", or a fragment

Output Schema

Name	Required	Description	Default
`error`	No
`terms`	No
`source`	No
`book_url`	No
`provider`	No
`disclaimer`	No
`data_updated`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 25, 2026

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

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 7, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already establish read-only, idempotent, closed-world reads, but the description adds substantive behavioral context beyond them: ~48% of departures state no destination, totals are a floor due to non-deregistration, and the 2015/2016 definitional break. It also discloses the licensing/attribution obligation.

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?

Information is front-loaded (source, scope, then caveats) and nearly every sentence carries signal. It is dense and reads somewhat as a wall of text, which slightly hurts scannability, but nothing is filler.

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 present, the description need not describe return values, and it covers the remaining risk areas: data caveats, temporal comparability limits, and the named-base denominator. An agent has everything needed to call and interpret it correctly.

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% and the schema already documents defaults and examples ('2025', 'Schweiz'). The description's 'Pass year, destination or top' only restates parameter names without adding format or interpretation rules, so the baseline 3 applies.

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?

Names the specific resource (German citizen emigration flows by destination country and year), the underlying statistic (Destatis 12711-0008), and the returned measures (departures, arrivals, net migration, share of named base). An agent can distinguish this from siblings like get_wealth_atlas or get_mobility_optionality 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete invocation guidance ('Pass year, destination or top') and explicit constraints ('Never trend across 2015/2016', 'rankings describe the named base only'). It stops short of naming a sibling alternative for related questions, so it is clear context without full when/when-not routing.

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

All Mirabello Immigration Intelligence 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.