codecite
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODECITE_DATABASE_URL | No | PostgreSQL connection string for the codecite database, e.g. postgresql://codecite:codecite@127.0.0.1:5432/codecite. | |
| CODECITE_EMBED_PROVIDER | No | Embedding provider to use; set to 'fake' to use the dependency-free hashed-bag-of-words embedder for CI-style runs. | |
| CODECITE_ENABLE_INGEST_TOOL | No | Set to '1' to enable the ingest_document tool; disabled by default. |
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 |
|---|---|
| search_codeD | – |
| get_sectionD | – |
| get_contextA | What surrounds a section: parent chain up to the chapter, previous/next siblings, children, and the sections that reference it. Use for 'where does this sit' or 'what else applies' questions. |
| resolve_referenceA | Parse free text for section/table/chapter references and report which ones exist in the index. |
| list_corporaA | List indexed corpora with their documents (layer, version), section/chunk counts, and the embedding model. Call this to tell the user what is actually indexed before answering. |
| list_chaptersC | Table of contents: chapter numbers and titles for one corpus. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| code_question | Answer a building-code question with citations, or say the corpus does not cover it. |
| compare_to_standard | Side-by-side: code requirement vs internal standard, with citations; flag which is stricter. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Tool names are distinct and suggest different purposes (context, reference resolution, corpus listing, code search, section retrieval, chapter listing). However, two tools (search_code, get_section) have empty descriptions, which slightly reduces clarity and could cause ambiguity in edge cases.
All tool names follow a consistent verb_noun pattern (get_context, resolve_reference, list_corpora, search_code, get_section, list_chapters). The verbs are varied but the structure is uniform and predictable.
With 6 tools, the set is well-scoped for a code citation/reference server. It covers lookups, searches, and structural navigation without being overly granular or excessive.
The tool set appears to cover core operations: searching code, retrieving sections and chapters, resolving references, and listing corpora. Missing operations like creating or updating references are likely outside the server's purpose, but the empty descriptions for two tools leave some uncertainty about full coverage.