ot-dossier-mcp
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| assemble_target_disease_evidenceC | Replay frozen evidence for NOD2/TNF and IBD. Returns scoped records and typed missingness. |
| validate_dossier_referencesC | Check references and structured assertions against a previously assembled packet. Not entailment. |
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 distinct verbs and roles: one assembles/replays evidence, the other validates references against an assembled packet. They are part of the same pipeline, which introduces mild sequencing ambiguity, but a careful reading of the descriptions clearly separates their purposes.
Both tools use snake_case with a leading verb (assemble_..., validate_...) and noun-phrase tails. The verb_noun pattern is consistent throughout, with no style mixing.
Only 2 tools is on the thin side, though the server's scope (a single frozen evidence dossier workflow) is narrow enough that this is borderline rather than clearly wrong. A few more operations would make it feel better scoped.
The surface covers an assemble-and-validate loop but appears locked to one hardcoded disease pair (NOD2/TNF and IBD) with no discovery, listing, or update operations, and no way to build or modify the underlying packet. Notable gaps remain for a general dossier workflow.