nodiom-mcp
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nodiom_readA | Returns the Markdown content at a structural location in a file. Use a selector like "# Heading > ## Subheading" to address any section. Use "# H1 > ## H2 > li[0]" to read a specific list item. Returns the raw Markdown string of the matched content. |
| nodiom_read_listA | Returns all list items under a selector as a JSON array of strings. Useful when you need to iterate over tasks, team members, or any bullet list. |
| nodiom_writeA | Replaces the content at a structural location with new content. The heading itself is preserved — only the body content is replaced. All other sections in the document are untouched. |
| nodiom_appendA | Appends new content after the last item in a section. Use this to add a new task, log entry, or note without disturbing existing content. Content is added at the end of the matched section. |
| nodiom_deleteA | Removes the node or section matched by the selector. Use "## Section > li[0]" to delete the first list item. Use "## Section" to delete an entire section including its heading. All other content is untouched. |
| nodiom_queryA | Returns structural metadata about a location: whether it exists, its type, depth, and child count. Use this to check if a section exists before reading or writing to it. |
| nodiom_treeA | Returns the full structural outline of a Markdown document as a nested JSON tree of headings. Use this to understand the structure of a document before reading or modifying it. |
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 7 tools
Each tool targets a distinct operation on the Markdown structure: reading content, reading list items, writing, appending, deleting, querying metadata, and viewing the outline. There is no meaningful overlap that would cause an agent to select the wrong tool.
Tools consistently use the nodiom_ prefix with lowercase snake_case names. Most are verb-based (read, write, append, delete, query), though 'tree' is a noun rather than a verb and could have been 'get_tree' for full consistency.
Seven tools is a well-scoped set for structured Markdown editing. Each tool covers a distinct need without redundancy or bloat, and the count is appropriate for the server's focused purpose.
The toolset covers read, write, append, delete, and structural inspection well. A minor gap is the lack of an explicit create-section operation; a selector must presumably reference an existing heading, so creating wholly new sections may require workarounds.