odt-mcp-server
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_odt | Læser tekst fra en .odt (OpenDocument Text) fil |
| get_odt_metadataA | Henter metadata fra en .odt fil (forfatter, titel, dato, osv.) |
| list_odt_filesB | Lister alle filer indeholdt i .odt arkivet |
| extract_odt_xmlA | Udtrækker rå XML fra en specifik fil i .odt arkivet (content.xml, styles.xml, meta.xml) |
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 distinctly different purpose: metadata retrieval, file listing, and XML extraction from ODT archives. No overlap or ambiguity.
All tool names follow the same verb_odt_noun pattern (get, list, extract) with consistent snake_case and meaningful verbs.
Three tools is a reasonable size for a focused read-only ODT server. It covers core read operations without unnecessary bloat, though it could benefit from slightly more depth.
Covers metadata, file enumeration, and raw XML extraction, but lacks tools for extracting plain text or converting formats. The set is adequate for basic inspection but leaves agents to parse XML themselves.