mcp-commune-france
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| commune_france_get_sourcesA | List curated sources used by this MCP. |
| commune_france_fetch_source_excerptB | Fetch a short text excerpt from a curated source by index or title keyword. |
| commune_france_find_communeA | Resolve French communes by name, INSEE code, or postal code using geo.api.gouv.fr. |
| commune_france_list_department_communesB | List communes in a French department using geo.api.gouv.fr. |
| commune_france_profileB | Build a source-oriented commune profile with geo identity and suggested public-data queries. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct purpose: source list, source excerpt, commune resolution, department listing, and profile building. No overlap exists between finding a specific commune and listing all communes in a department, and the profile combines earlier data without redundancy.
All tools share the 'commune_france_' prefix and follow a verb_noun pattern (get, fetch, find, list, profile). The only deviation is 'profile' as a noun, but it functions as a verb-like action and remains uniform with the prefix, making the pattern predictable.
Five tools is well within the optimal range for a focused server. Each tool covers a discrete part of the domain—sources and commune data—without unnecessary expansion or redundancy.
The server covers its stated purpose completely: retrieving source metadata, fetching excerpts, resolving communes, listing department communes, and building a composite profile. There are no obvious missing operations for a read-only, data-retrieval service.