Humanitarian MCP

Export data

export_data

Read-only

Export normalized humanitarian records as CSV, JSON, Markdown, or GeoJSON. Filter by dataset, country, year, and role to obtain raw data for analysis or sharing.

Instructions

Export normalized records from any dataset as csv, json, markdown or geojson (geojson only makes sense with group_by set, so rows map to countries). Use this when the user wants raw data to download or paste elsewhere.

Input Schema

TableJSON Schema

Name	Required	Description
`role`	No	"asylum" = people hosted IN the country; "origin" = people displaced FROM the country
`limit`	No	Max rows (default 500)
`format`	Yes	Serialization format
`country`	No	Filter by country (name or ISO3)
`dataset`	Yes	population \| demographics \| asylum-applications \| asylum-decisions \| context-indicators \| idps \| conflict-events \| humanitarian-funding \| food-security
`year_to`	No	Last year of the range (default: latest available)
`group_by`	No	Break rows down per asylum or origin country instead of aggregating
`year_from`	No	First year of the range (default: 10 years back)
`include_codebook`	No	Attach a codebook documenting every exported variable (meaning, unit, derivation) — ready for a paper's data appendix. Default false.
`include_manifest`	No	Attach an extraction manifest (exact arguments, timestamp, server version, citation) for reproducibility. Default true.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`format`	Yes
`dataset`	Yes
`codebook`	No
`manifest`	No
`row_count`	Yes
`truncated`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.6.0Jul 10, 2026

changedInput schema / properties / dataset / enum

Previous value: -[
-  "population",
-  "demographics",
-  "asylum-applications",
-  "asylum-decisions",
-  "context-indicators",
-  "idps",
-  "conflict-events",
-  "humanitarian-funding",
-  "food-security"
-]New value: +[
+  "population",
+  "demographics",
+  "asylum-applications",
+  "asylum-decisions",
+  "context-indicators",
+  "idps",
+  "conflict-events",
+  "humanitarian-funding",
+  "food-security",
+  "situation-reports"
+]

Changed6 schema fields changedv0.5.1Jul 10, 2026

changedInput schema / properties / dataset / description

Previous value: -"population | demographics | asylum-applications | asylum-decisions"New value: +"population | demographics | asylum-applications | asylum-decisions | context-indicators | idps | conflict-events | humanitarian-funding | food-security"

changedInput schema / properties / dataset / enum

Previous value: -[
-  "population",
-  "demographics",
-  "asylum-applications",
-  "asylum-decisions"
-]New value: +[
+  "population",
+  "demographics",
+  "asylum-applications",
+  "asylum-decisions",
+  "context-indicators",
+  "idps",
+  "conflict-events",
+  "humanitarian-funding",
+  "food-security"
+]

addedInput schema / properties / include_codebook

Added value: +{
+  "description": "Attach a codebook documenting every exported variable (meaning, unit, derivation) — ready for a paper's data appendix. Default false.",
+  "type": "boolean"
+}

addedInput schema / properties / include_manifest

Added value: +{
+  "description": "Attach an extraction manifest (exact arguments, timestamp, server version, citation) for reproducibility. Default true.",
+  "type": "boolean"
+}

addedOutput schema / properties / codebook

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "description": {
+        "type": "string"
+      },
+      "field": {
+        "type": "string"
+      },
+      "unit": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "field",
+      "description",
+      "unit"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / manifest

Added value: +{
+  "additionalProperties": {},
+  "type": "object"
+}

First observedv0.1.0Jul 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly and openWorld hints. The description adds that it exports normalized records and mentions format-specific behavior (geojson requires group_by), which is helpful beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the main action and available formats. No unnecessary words.

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?

Output schema exists, so return values are covered. The description includes the key behavioral nuance about geojson and group_by. With 10 parameters, it could add more context about filtering options, but the schema descriptions fill in the gaps.

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 coverage is 100%, so the description adds limited extra meaning beyond the schema descriptions. The geojson/group_by hint provides some value, but for 10 parameters, the description does not elaborate on most.

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 clearly states the tool exports normalized records from any dataset in multiple formats, and the context of geojson with group_by differentiates it from sibling tools that focus on analysis or visualization.

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 description explicitly says to use when the user wants raw data to download or paste elsewhere, and notes the geojson caveat with group_by. It does not explicitly state when not to use, but the purpose is clear enough.

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