Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
mayotte_get_sourcesA

List curated official and high-value sources for Mayotte.

mayotte_search_data_gouvB

Search public datasets on data.gouv.fr using the official public API.

mayotte_get_datasetA

Inspect one data.gouv.fr dataset by slug or id using the official public API.

mayotte_fetch_source_excerptA

Fetch a short text excerpt from one curated source URL. Use source_key as a number, title keyword, or URL fragment from get_sources.

mayotte_explain_scopeA

Explain what this MCP is useful for and how an agent should combine its sources.

mayotte_list_reference_itemsB

List built-in reference items for this MCP, when available.

mayotte_list_communesA

List Mayotte communes from geo.api.gouv.fr with INSEE code, postal codes, population, and center geometry.

mayotte_find_communeA

Find a Mayotte commune by name, INSEE code, or postal code using geo.api.gouv.fr.

mayotte_search_datasetsB

Search data.gouv.fr for Mayotte-specific datasets, optionally adding a topic.

mayotte_get_vigilanceA

Return official Mayotte Météo-France vigilance URL and a short public page excerpt.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 10 tools

Disambiguation3/5

mayotte_search_data_gouv and mayotte_search_datasets both target the same data.gouv.fr dataset search and could be confused, and list_reference_items is vague next to get_sources. Otherwise the tools separate fairly clearly into dataset, commune, source, and vigilance functions.

Naming Consistency5/5

All tools consistently use the mayotte_ prefix with lowercase snake_case and clear verb-object combinations such as list_communes, find_commune, get_vigilance, and fetch_source_excerpt. The naming pattern is uniform and predictable.

Tool Count5/5

Ten tools is well within the ideal range for a regional information server. Each tool contributes to a distinct area such as datasets, communes, sources, or vigilance without unnecessary bloat.

Completeness4/5

The tool surface covers the core read-only workflows: searching and retrieving datasets, looking up communes, listing curated sources, and getting vigilance information. Minor gaps exist, such as no dedicated commune detail tool and some vagueness around reference items, but agents can work around them.

Maintenance

ActivityMaintained
ResponsivenessNo issues