Skip to main content
Glama
datagouv

datagouv-mcp

by datagouv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Search datasets

search_datasets
Read-onlyIdempotent

Search for datasets on the French open data platform by keyword, with optional sorting and filtering by update date.

Instructions

Search for datasets on data.gouv.fr by keywords.

This is typically the first step in exploring data.gouv.fr. Use short, specific queries (the API uses AND logic, so generic words like "données" or "fichier" may return zero results).

Use sort to order results. Accepted values: created, last_update, reuses, followers, views. Optionally prefixed with '-' for descending (e.g. -last_update). Use last_update_range to restrict results to recently updated datasets: last_30_days, last_12_months, last_3_years.

Typical workflow: search_datasets → list_dataset_resources → query_resource_data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
sortNo
queryYes
page_sizeNo
last_update_rangeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removedv0.2.30
  3. Changed2 schema fields changedv0.2.26
    • addedInput schema / properties / last_update_range
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Last Update Range"
+}
    • addedInput schema / properties / sort
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Sort"
+}
  4. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover readOnly/openWorld/idempotent behavior. The description adds valuable behavioral context, such as the API using AND logic and the effect of generic keywords, and documents accepted sort and range values.

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 tightly organized: purpose, usage tips, parameter specifics, and a workflow example. It is concise and front-loads the core function without unnecessary verbosity.

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?

For a tool with 5 parameters and an output schema, the description provides sufficient operational context, including parameter constraints and the expected workflow chain. No critical information is missing.

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

Parameters4/5

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

Despite 0% schema coverage, the description explains the semantics of query, sort, and last_update_range in detail. Page and page_size are left to their self-evident names and defaults, which is acceptable.

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: 'Search for datasets on data.gouv.fr by keywords.' It also positions it as 'typically the first step in exploring data.gouv.fr,' distinguishing it from sibling tools like list_dataset_resources and query_resource_data.

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

Usage Guidelines5/5

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

Provides explicit guidance on when and how to use the tool: 'This is typically the first step,' plus specific tips on query construction, accepted sort values, last_update_range options, and a typical workflow. This leaves little room for misuse.

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