mcp-server

German Emigration Flows by Destination

get_emigration_flows

Read-only

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.

Input Schema

TableJSON 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

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

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only declare readOnly/openWorld/destructive hints, but the description adds substantive behaviour: a caveats field, the fact that ~48% of departures name no destination so rankings describe a partial base, that totals are a floor, a definitional break, and licence/attribution obligations. This is exactly the beyond-annotations disclosure the dimension rewards.

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?

It is front-loaded with the data's identity and scope, and labelled cues (OFFICIAL, CRITICAL) aid scanning. The illustrative 2025 figures are useful colour but make the block longer than strictly necessary, keeping it out of the top band.

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?

Coverage is exhaustive for an agent's needs: source, time span, returned measures, base-population caveat, definitional break and licensing are all present, and an output schema already handles the exact return shape. Nothing needed to call the tool correctly is missing.

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 the schema already documents year, destination and top; the description only restates them ('Pass year, destination or top'). Baseline 3 is appropriate since the schema does the heavy lifting and the description adds no format or fallback detail beyond it.

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?

The description names a specific verb+resource (emigration flows by destination country and year), pins the exact source (Destatis statistic 12711-0008, 2016 onwards) and states the returned measures (departures, arrivals, net migration, destination share). It is unmistakably distinct from the surrounding citizenship/visa/programme siblings.

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?

It gives clear usage context ('Pass year, destination or top'), flags the analyst caution 'Popularity is not suitability', and warns against trending across 2015/2016. It never names an alternative sibling or states explicitly when not to use it, so it stops short of the explicit routing that earns a 5.

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.