Muninn
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 |
|---|---|
| searchA | Semantic search over the corpus. Returns chunks with page-level citations. Args: query: natural-language question or topic. top_k: number of results (default 6). doc_id: restrict to one document (from list_documents), "" = all. note_type: which payload types to search — "raw" (verbatim paper text, ground truth), "claude_note" (Claude's reading notes), "hyde" (generated HyDE bridges only), "all" (raw + claude_note, the default), or "everything" (raw + claude_note + hyde). hypothesis: HyDE fallback. When the plain query misses (low scores), pass a short hypothetical answer paragraph here. It is embedded and averaged with the query (Gao et al., 2023) to retrieve REAL corpus chunks via the hypothesis. Each hit is tagged retrieved_via="hyde". "" = ordinary query-vector search (retrieved_via="direct"). |
| save_hydeA | Persist a HyDE hypothetical document as a reusable type=hyde bridge. Use after a search(query, hypothesis=...) fallback produced good grounding, so the same retrieval miss becomes an indexed hit next time (searchable via note_type="hyde" or "everything"). A hyde bridge is generated text, never a citable source. Idempotent per (doc_id, query) — re-saving updates in place. Args: query: the user query this hypothesis answers (used for the bridge id). hypothesis: the hypothetical answer paragraph to store and embed. doc_id: optional document this bridge is about ("" = corpus-wide). title: optional label ("" = derived from the query). |
| list_documentsA | List all documents in the knowledge base with doc_id, title, and pages. |
| get_pageA | Full text of one page of a document — for reading context around a search hit. Args: doc_id: document id from search/list_documents. page: 1-based page number. |
| get_citationA | APA-7 citation for a document: in-text (parenthetical + narrative) and the full reference-list entry. Use these verbatim when writing — the corpus is APA only, never mix styles. For a direct quote, add the page to the in-text form: '(Author, Year, p. N)'. Args: doc_id: document id from search/list_documents. |
| render_pageA | Render a PDF page as an image, optionally with a passage highlighted. Use after search/get_page to SHOW the user the exact source location. Args: doc_id: document id from search/list_documents. page: 1-based page number. highlight: passage to highlight. Verbatim raw-chunk text from search() always works; paraphrases usually work too — matching falls back exact -> sentence pieces -> fuzzy word alignment -> semantic (embeds the text and highlights the nearest raw chunk on this page). Returns the image plus a highlight_method report. "" = no highlighting. |
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 6 tools
Every tool has a clearly distinct purpose: listing documents, getting page text, retrieving citations, rendering pages, saving hypothetical documents, and searching. No overlap or ambiguity.
Most tool names follow a verb_noun pattern (list_documents, get_page, get_citation, render_page, save_hyde). 'search' is a single verb but is a standard exception for search functionality. Overall consistent.
Six tools is well-scoped for a knowledge base server covering listing, reading, citation, rendering, saving, and searching. Each tool is essential and not excessive.
The tool set covers core read operations and search with HyDE support, plus citation and visualization. Missing write/update operations for raw documents, but intentional for a knowledge base. Minor gap for editing documents.