Skip to main content
Glama
Sign In
mcp-madagascar

mcp-madagascar

by Hug0x0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

madagascar_search_hdx_datasets

Search Humanitarian Data Exchange (HDX) for Madagascar datasets via CKAN API. Find humanitarian, weather, risk, and open-data sources for Madagascar.

Instructions

Search HDX / Humanitarian Data Exchange for Madagascar datasets using the CKAN API.

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

Input Schema

NameRequiredDescriptionDefault
rowsNoNumber of datasets to return.
queryNoHDX search query.Madagascar

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not disclose side effects, read-only nature, rate limits, or error behavior. The mention of CKAN API is minimal and does not address behavioral details.

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?

The description is a single concise sentence with no unnecessary information. It is well-structured and to the point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is minimal and does not explain the return format or any output specifics. Given the simple schema and lack of output schema, it is somewhat complete, but could benefit from stating what the search returns (e.g., list of datasets).

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?

Both parameters (rows and query) are described in the schema with clear meanings. The tool description adds no additional context beyond the schema, so it meets the baseline for high schema coverage.

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's purpose: searching HDX for Madagascar datasets via CKAN API. It distinguishes from sibling tools like search_data_gouv and get_dataset.

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 implies usage for HDX Madagascar searches, but does not explicitly contrast with alternative search tools or state when not to use it. It is clear enough for the intended use case.

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

Deploy Server

Other Tools