Skip to main content
Glama
cturkieh

France Data MCP

by cturkieh
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

etablissements_finess_in_radius

Read-onlyIdempotent

Search for FINESS healthcare facilities within a geographic radius. Filter results by establishment type (e.g., MCO, EHPAD, pharmacies) for targeted queries.

Instructions

Recherche d'établissements de santé FINESS dans un rayon géographique (PostGIS ST_DWithin). Filtrable par familles. 24 valeurs 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 (dump CSV ingéré localement). Note : champ email toujours null (non exposé par FINESS public).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lonYesLongitude du centre (WGS84).
latYesLatitude du centre (WGS84).
radius_kmNoRayon en km (0.1-50, défaut 5).
famillesNoFamilles FINESS à inclure (24 valeurs disponibles, voir enum). Si omis, toutes catégories.
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.3/5.0
Behavior4/5

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

The description adds behavioral context beyond annotations, such as the email field always being null and the data source (FINESS/DREES dump). Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, so the description supplements this well without contradiction.

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 two sentences plus a note, concise and front-loaded with the core functionality. Every sentence serves a purpose, with 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 (6 parameters, well-documented in schema, no output schema), the description is complete. It covers purpose, filtering, data source, and a behavioral caveat, leaving no obvious gaps.

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?

Input schema has 100% description coverage, so baseline is 3. The description adds value by enumerating the 24 family values and noting the email field behavior, providing meaning beyond the schema. However, it does not add significant detail on other parameters.

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 searches for FINESS health establishments within a geographic radius using PostGIS, and mentions filtering by 24 family types. This is specific and distinguishes it from sibling tools like 'professionnels_in_radius' or 'etablissements_finess_by_categorie'.

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

Usage Guidelines3/5

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

The description explains when to use the tool (search by radius and optional family filter) but does not explicitly mention when not to use it or alternatives. Given the sibling list, it provides adequate context but no exclusions or comparisons.

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