Skip to main content
Glama

Hdx

by io.github.pipeworx-io

Search Datasets

search_datasets
Read-onlyIdempotent

Search the Humanitarian Data Exchange catalogue (CKAN package_search) for datasets on displacement, refugees, food security, conflict, disasters, health, population, etc. Returns matching datasets with titles, descriptions, publishing organization, locations (groups), and resources. Filter by country/crisis with fq="groups:" (e.g. "groups:syr") — get codes from list_locations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fqNoSolr filter query (facet filter). e.g. "groups:syr" (location = Syria), "organization:unhcr", "res_format:CSV". Combine with spaces.
rowsNoMax results, 1-1000 (default 25).
sortNoSort spec, e.g. "metadata_modified desc" or "score desc".
queryYesSearch terms, e.g. "displacement", "food security", "conflict fatalities".
startNo0-based offset for paging.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations indicate readOnlyHint, openWorldHint, idempotentHint, destructiveHint=false. The description adds behavioral context: source (CKAN package_search), return fields (titles, descriptions, etc.), and filter capabilities, without contradicting 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 concise sentences front-loading purpose. Every sentence adds value; no filler.

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?

Fairly complete for a search tool with 5 parameters and no output schema. Explains source, return fields, filtering, and references sibling. Could detail output format more, but adequate.

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

Parameters5/5

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

Schema coverage is 100%, baseline 3. Description adds significant meaning: explains fq usage with examples, suggests list_locations for codes, elaborates on query and sort. This goes well 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?

The description clearly states the tool searches the Humanitarian Data Exchange catalogue for specific topics like displacement, refugees, etc., and returns datasets with details. It distinguishes from siblings like list_locations by referencing them for codes.

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 explains when to use the tool (searching humanitarian datasets) and gives a concrete filter example with fq and reference to list_locations. It lacks explicit when-not-to-use statements but provides clear context.

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

All Hdx toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation2/5

Multiple tools have overlapping purposes (e.g., three variants of ask_pipeworx, several polymarket tools, and multiple discovery/entity tools). Despite detailed descriptions, the similiar functionalities create confusion for an agent selecting among them.

Naming Consistency3/5

Tool names are consistently in snake_case but the verb/noun pattern is mixed: some start with verbs (ask_, list_, remember_), others with nouns (entity_profile, polymarket_edges). This inconsistency reduces predictability.

Tool Count2/5

35 tools is high for a single server, especially when the scope spans two disparate domains (HDX humanitarian data and Pipeworx data platform). Many tools could be logically split into separate, more focused servers.

Completeness3/5

The tool set covers a wide range of functionality (data retrieval, comparison, monitoring, memory) but has notable gaps: no direct data download tool for HDX resources, no account management, and no exploration of Pipeworx packs beyond discover_tools.

Resources