Enma Daio
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ENMA_INDEX | Yes | Path to the scan index file. | |
| ENMA_STORE | Yes | Path to the file where memorized rules are stored. | |
| ENMA_REJETS | No | Path to the file for rejected candidate rules. | |
| ENMA_CATALOGUE | Yes | Path to the enma-catalogue.json configuration file containing roots, forbidden zones, confirmation zones, and name exclusions. |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resoudre_destinationC | Propose une destination pour un contenu (mode conseil : Enma propose, le harnais écrit). |
| memoriser_regleC | Mémorise ou modifie une règle de classement (projet/gabarit). Une exception fichier n'est jamais persistée. |
| lister_reglesA | Liste les règles de classement mémorisées. |
| proposer_regleC | Propose une règle candidate à faire valider, à partir d'une destination observée. |
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 4 tools
Each tool serves a distinct function: resolving a destination, memorizing/modifying rules, listing rules, and proposing new rules based on observations. There is no overlap or ambiguity between them.
All tool names follow a consistent pattern of infinitive verb + underscore + noun in French (e.g., resoudre_destination, memoriser_regle). The style is uniform and predictable.
With 4 tools, the set is well-scoped for a rule-based classification system. Each tool addresses a core need (resolution, rule management, listing, and suggestion) without unnecessary bloat.
The main workflows are covered (resolve, create/update, list, propose), but there is no delete operation for rules. This is a notable gap that could hinder rule maintenance, though agents might work around it by modifying rules instead.