Skip to main content
Glama
datagouv

datagouv-mcp

by datagouv

Search organizations

search_organizations
Read-onlyIdempotent

Search and filter organizations that publish datasets and reuses on data.gouv.fr. Use criteria like name, badge, or business number to narrow results.

Instructions

Find publishing organizations on data.gouv.fr (who publishes datasets and reuses).

Pass a short query with distinctive words (acronym, ministry name, city, "INSEE", etc.). Generic or very broad terms often return large result sets; combine with page / page_size or add badge / name / business_number_id when you need a narrow list.

Leave query empty to list organizations with pagination (same as browsing the catalog). Use sort to order results (e.g. name, datasets, reuses, followers, views, created, last_modified, or the same with a leading '-' for descending, such as -datasets).

badge filters by publisher type: public-service, certified, association, company, local-authority.

The reply includes how many organizations matched, the current page, and for each hit: name (and acronym if any), id, slug, badges, optional usage metrics, and links to the organization page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNo
pageNo
page_sizeNo
sortNo
badgeNo
nameNo
business_number_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, which align with the description's mention of search functionality. The description adds detail about the response structure (matched count, page, per-org data with metrics and links) 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?

The description is concise with four sentences, each serving a purpose: stating the tool's function, offering usage tips, detailing pagination, and listing sort options. It is well-structured and front-loaded.

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?

Given the 7 parameters (0 required), presence of output schema, and clear annotations, the description covers all necessary aspects: search behavior, filtering, sorting, pagination, and response details. It is fully complete.

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?

Despite 0% schema description coverage, the description explains all parameters well: query, page, page_size, sort (with examples), badge (with allowed values), name, and business_number_id. It provides meaningful context that the schema lacks.

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: 'Find publishing organizations on data.gouv.fr'. It provides specific use cases like searching by acronym, ministry, city, and 'INSEE', which distinguishes it from sibling tools that search datasets or dataservices.

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?

The description gives explicit guidance on when to use the tool (short query, combine with filters) and when not to (generic broad terms). It also advises on alternatives to narrow results using badge, name, or business_number_id, and states that leaving query empty lists all organizations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/datagouv/datagouv-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server