space-stds
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPACE_STDS_DATA_DIR | No | Directory to store the SQLite index and other runtime data. Defaults to ~/.local/share/space-stds. | |
| SPACE_STDS_CORPUS_DIR | No | Directory containing authorised standards PDFs, corpus files, and manifests. Defaults to ~/.local/share/space-stds/corpus. | |
| SPACE_STDS_PDF_BACKEND | No | PDF extraction backend to use: 'pypdf' (default) or 'pdf-inspector'. | pypdf |
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_standardsA | Rank locally indexed CCSDS and ECSS passages by meaningful query terms. Returns exact source provenance; an empty list means no passage matched enough distinct meaningful terms. |
| get_documentA | Get authoritative metadata for one indexed document edition. Specify revision when more than one edition is indexed. |
| get_passageA | Retrieve one exact passage by the opaque identifier returned by search_standards. |
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 3 tools
Each tool has a clearly distinct role: search_standards finds passages, get_document returns metadata, and get_passage retrieves a specific passage by ID. There is no meaningful overlap between them.
All tool names follow the same verb_noun snake_case pattern: search_standards, get_document, get_passage. The naming is uniform and predictable.
Three tools is well-scoped for a focused standards-search and retrieval server. Each tool covers a necessary step in the workflow without unnecessary bloat.
The search-to-passage retrieval workflow is complete, but there is no tool to list all indexed documents or fetch full document content. These are minor gaps that can be worked around via search and metadata access.