dataroom
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATAROOM_DATA | No | Path to a JSON file containing the data room. If not set, the fictive data room is used. | |
| DATAROOM_MCP_TOKEN | No | Secret token required when the server is exposed to the network (e.g., --host 0.0.0.0). Without it, the server refuses to start in network mode. |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_data_roomA | Recherche dans la data room : filtres sur les métadonnées et/ou recherche plein texte dans les articles. Sans |
| get_contractB | Renvoie le texte d'un contrat, découpé par article, pour vérifier ou citer une clause précise. |
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 2 tools
The two tools have clearly distinct purposes: search_data_room locates contracts or articles via filters/full-text search, while get_contract retrieves the complete text of a specific contract. There is no overlap in functionality, so an agent can easily select the right tool.
Both names follow a consistent verb_noun snake_case pattern: search_data_room and get_contract. The verbs (search, get) clearly indicate the action, and the nouns refer to the domain resources in a predictable way.
With only two tools, the set is on the thin side for a data room server that might involve contract management, metadata browsing, and article-level access. While the two tools cover the core read operations, the count feels minimal and borderline for the apparent scope.
The tools cover the essential read lifecycle: search/filter contracts and retrieve full contract text with articles. Minor gaps exist, such as direct article-level retrieval or explicit metadata-only queries, but agents can work around these using the provided tools.