Skip to main content
Glama
cturkieh

France Data MCP

by cturkieh
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

etablissements_finess_by_categorie

Read-onlyIdempotent

List FINESS healthcare and social facilities by category, with optional department or commune filters. Covers 24 facility types for exhaustive area enumeration.

Instructions

Liste des établissements FINESS par famille, avec filtre département ou commune optionnel. Pas de rayon — pour énumération exhaustive d'une zone administrative. 24 familles disponibles : mco, ssr, sld, had, psychiatrie, dialyse, ambulatoire, labo, imagerie, pharmacie, msp_cpts, ehpad, residence_autonomie, senior_accompagnement, ssiad, aide_domicile, handicap_enfants, handicap_adultes, addictologie, enfance_protection, pmi, hebergement_social, prevention_sante, groupement. Source : FINESS / DREES. Note : champ email toujours null (non exposé par FINESS public).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categorieYesFamille FINESS recherchée (24 valeurs disponibles, voir enum).
departementNoCode département INSEE (ex: '75', '2A', '2B', '971'). Métropole 2 caractères (Corse '2A'/'2B', pas '20'), DOM/TOM 3 caractères. Optionnel.
code_inseeNoCode INSEE de commune (5 caractères). Optionnel.
limitNoNombre max de résultats (1-500, défaut 100).
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`).

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds useful behavioral context beyond annotations: the email field is always null (not exposed by FINESS public) and the include_freshness parameter behavior. 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 front-loaded with purpose and usage. It is slightly verbose due to listing all 24 families inline (redundant with schema enum), but each sentence adds value. Could be more concise, but overall well-structured.

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 complexity (5 parameters, 1 required) and the presence of an output schema, the description covers purpose, filters, families, data source, and a notable behavioral quirk (null email). It provides sufficient context for an agent to use the tool correctly.

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?

Schema coverage is 100%, with each parameter already having a detailed description. The description adds the note about no radius filter but does not significantly enhance understanding of the parameters beyond what the schema provides. Baseline 3 is appropriate.

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 'Liste des établissements FINESS par famille' and distinguishes from sibling tools like 'etablissements_finess_in_radius' by specifying 'Pas de rayon — pour énumération exhaustive d'une zone administrative'. It provides a specific verb ('liste') and resource ('établissements FINESS par famille') with optional filters.

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 explicitly contrasts this tool with radius-based alternatives ('Pas de rayon') and describes its use case as exhaustive enumeration of an administrative zone. It also lists the 24 available families, giving agents clear context for when to use this tool.

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