Skip to main content
Glama
cturkieh

France Data MCP

professionnels_rpps_par_dept

Read-onlyIdempotent

List health professionals by French department (RPPS). Filter by profession, specialty, practice mode. Use for counting salaried or total staff. Supports pagination.

Instructions

Listing départemental de PS via RPPS (libéraux + salariés). Filtres optionnels : profession_code, savoir_faire_code, mode_exercice_code. Re-paginer via offset tant que truncated=true. Préférer professionnels_par_specialite_dept (Ameli) pour les libéraux conventionnés ; cet outil sert à compter ou lister les salariés / l'effectif total. Par défaut, ne renvoie que les PS de catégorie Civil (C) — droit privé : libéraux, salariés privés, hospitaliers contractuels, ~97 % de la base. Passer include_agents_publics: true pour inclure aussi les Agents publics (M) — fonctionnaires d'État + collectivités + militaires SSA, ~0,3 % (PH titulaires, médecins inspecteurs ARS, médecins conseils CNAM, médecins scolaires Éducation nationale, médecins PMI). Passer include_etudiants: true pour inclure aussi les Étudiants (E) — internes, externes, élèves IDE/SF, ~2,5 %. Source nomenclature : https://mos.esante.gouv.fr/NOS/TRE_R09-CategorieProfessionnelle/. Source : Annuaire Santé, Agence du Numérique en Santé (ANS) — Licence Ouverte v2.0

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
departementYesCode département INSEE (ex: '75', '2A', '2B', '971'). Métropole 2 caractères (Corse '2A'/'2B', pas '20'), DOM/TOM 3 caractères.
profession_codeNoCode profession ANS (ex: '10' Médecin, '60' Infirmier). Optionnel.
savoir_faire_codeNoCode savoir-faire ANS (spécialité fine DES/DESC). Optionnel.
mode_exercice_codeNoCode mode d'exercice ANS (libéral / salarié / mixte). Optionnel.
include_etudiantsNo
include_agents_publicsNo
limitNoNombre max de résultats par page (défaut serveur 100).
offsetNoOffset pour pagination (défaut 0). Re-paginer tant que `truncated=true`.
include_freshnessNoSi true, ajoute un champ `data_freshness` au payload (dans `query_metadata` si présent, sinon à la racine) listant la dernière ingestion réussie par source (FINESS, Ameli, RPPS) avec `staleness_days`. Opt-in pour ne pas alourdir les payloads par défaut. Cache 5min côté serveur — coût négligeable.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNombre d'entrées retournées dans `results` (post-troncature).
truncatedNotrue si le total réel dépasse `limit` (re-paginer via `offset` si supporté). Optional sur les tools de listing exhaustif (lister_*).
resultsYesEntrées métier (shape spécifique au tool, cf. description du tool).
query_metadataNoMetadata de la query (radius_km, departement, filtres appliqués, …).
freshnessNoFraîcheur des sources (présent si `include_freshness: true`).
Behavior5/5

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

Annotations already indicate read-only and idempotent behavior; the description adds valuable context such as default category (Civil), inclusion of other categories with percentages, pagination logic, and the optional freshness field. No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is thorough but slightly long; however, every sentence is informative and efficiently front-loads purpose, filters, pagination, and alternative tool. No wasted words.

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 tool's complexity (9 parameters, pagination, category variants), the description covers all necessary behavioral details: pagination, category inclusion options, alternative tool suggested, freshness opt-in, and data sources/license. Output schema handles return values.

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 78% and the description adds meaning to parameters like `include_agents_publics` and `include_etudiants` (explaining categories and percentages), `include_freshness` (behavior), and pagination with `offset` and `truncated`.

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 it lists healthcare professionals per department via RPPS, distinguishes from the sibling tool `professionnels_par_specialite_dept` by noting it is for salaried/total counts, and explains default category filtering.

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?

Explicitly recommends `professionnels_par_specialite_dept` for liberal conventionné, explains pagination with offset and truncated flag, and details how to include additional categories (agents publics, étudiants) with contextual hints.

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/cturkieh/france-data-mcp'

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