theosis-ancient-context-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CUC_CORPUS_DIR | No | Path to the local Copenhagen Ugaritic Corpus checkout. Required for the CUC local adapter to work. | |
| COPTSCRIPTORIUM_CORPUS_DIR | No | Path to the local Coptic SCRIPTORIUM corpus directory. Enables local search for Coptic texts when set. |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_corporaA | List all registered ancient text corpora with metadata. Returns registry records for TLA, Coptic SCRIPTORIUM, HPM/HDivT, CUC, DASI, OCIANA, CDLI, DPPC, CIP — each with source_type, language, period, access_status, source_url, licence notes, and integration notes. |
| get_corpus_statusA | Get detailed status for a specific corpus. Includes configured local path, availability checks, and version/commit info when discoverable. |
| search_corpusA | Search a corpus for a query string. For enabled/local adapters, returns matching results. For deferred or remote-only sources, returns an explicit not_ready/remote_only result with provenance envelope rather than failing ambiguously. |
| get_textB | Retrieve text content by reference identifier. For local adapters, returns bounded text with provenance. For deferred/remote-only sources, returns explicit status. |
| get_text_metadataA | Retrieve metadata for a text reference. For local adapters, returns file metadata and provenance. For deferred/remote-only sources, returns explicit status. |
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 targets a distinct resource and action: listing all corpora, checking one corpus's detailed status, searching within a corpus, retrieving text content, and fetching text metadata. There is no meaningful functional overlap, and even the status-related tools are cleanly separated by all-versus-one scope.
All tools use a consistent verb_noun snake_case pattern: list_corpora, get_corpus_status, search_corpus, get_text, get_text_metadata. Plural and singular nouns are used naturally for collection-level versus single-item operations, so the naming is predictable.
Five tools is a well-scoped size for a read-only ancient-text corpus access server. Each tool earns its place in the workflow without redundancy or unnecessary surface area.
The tool surface covers the apparent domain completely: discover available corpora, inspect corpus status, search for texts, retrieve text content, and retrieve metadata. Deferred or remote-only sources are handled explicitly rather than resulting in dead-end errors, and no CRUD operations are expected for this read-only context.