gilbert-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GILBERT_API_KEY | Yes | API key for Gilbert, format: glbrt_live_... | |
| GILBERT_BASE_URL | No | Base URL for Gilbert API | https://gilbert-assistant.ovh/api/v1 |
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 |
|---|---|
| list_meetingsA | Liste les réunions de l'utilisateur. Pagination et filtres par statut et date. Utile pour répondre à « quelles sont mes réunions récentes ? » ou « liste les réunions du mois dernier ». |
| get_meetingA | Récupère le détail complet d'une réunion : metadata + transcription + synthèse. Utile quand l'utilisateur veut résumer une réunion spécifique. |
| get_transcriptA | Récupère uniquement la transcription texte d'une réunion (plus léger que get_meeting). Format « Speaker 0: ...\nSpeaker 1: ... ». |
| get_summaryA | Récupère la synthèse markdown d'une réunion (plus léger que get_meeting). |
| search_meetingsA | Recherche full-text dans les titres, transcriptions et synthèses de l'utilisateur. Utile pour « trouve-moi la réunion où on a parlé de X ». |
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 and well-defined purpose: get_meeting returns full details, get_summary returns the summary, get_transcript returns the transcript, list_meetings lists meetings, and search_meetings performs full-text search. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case (get_*, list_*, search_*). This predictability helps the agent understand the action and resource for each tool.
With exactly 5 tools, the set is well-scoped for a meeting retrieval service. Each tool covers a core operation without being too many or too few.
The tool set is complete for reading and searching meetings, but lacks any write operations (create, update, delete). This is a notable gap for a meeting management server, limiting full lifecycle coverage.