Skip to main content
Glama
Sign In
mcp-madagascar

mcp-madagascar

by Hug0x0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

madagascar_search_data_gouv

Search public datasets on data.gouv.fr for Madagascar-related information.

Instructions

Search public datasets on data.gouv.fr using the official public 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_data_gouv"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoSearch query.Madagascar
page_sizeNoNumber of datasets to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 mentions 'official public API,' suggesting a read-only operation, but does not explicitly state side effects, rate limits, or error behavior. It also omits any indication of whether the operation is safe or destructive, leaving room for assumptions.

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 that directly states the tool's purpose. It avoids unnecessary words and is well-structured for quick comprehension.

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 covers the basic functionality but lacks context about return format, additional behaviors, or typical use cases. Given the presence of sibling tools, it would benefit from mentioning that this is specifically for French open data, but it remains minimally complete.

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?

The input schema provides descriptions for both parameters (query and page_size), covering semantics adequately. The tool description does not add further detail about the parameters, but since schema coverage is 100%, the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (search), resource (public datasets), and target platform (data.gouv.fr) using the official API. However, it does not explicitly differentiate from sibling tools like madagascar_search_hdx_datasets, though the mention of data.gouv.fr implies a distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives, such as madagascar_search_hdx_datasets. It lacks context about which data source is preferred or any exclusions, making it unclear for an agent to decide between similar search tools.

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