MarkScribe
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MARKS_ROOT | No | Root directory to serve (equivalent to --root flag) | Current working directory |
| MARKS_LOG_LEVEL | No | Log level (debug, info, warn, error, fatal) (equivalent to --log-level flag) | info |
| MARKS_SCHEMAS_DIR | No | Directory to load schema YAML files from (equivalent to --schemas-dir flag) | ~/.markscribe/schemas/ |
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_noteA | Returns |
| write_noteA | Writes content to a note. Pass |
| patch_noteA | Replaces a string within a note. Pass |
| delete_noteA | Deletes a note. Pass |
| move_noteA | Moves or renames a note. Pass |
| read_multiple_notesA | Batch-reads up to 10 notes. Pass |
| list_directoryA | Returns |
| get_statsA | Returns |
| switch_directoryA | Accepts |
| get_frontmatterA | Returns |
| update_frontmatterA | Sets and/or removes frontmatter keys. Pass |
| manage_tagsA | Add, remove, or list tags on a note. Pass |
| search_notesA | Full-text BM25 search. Pass |
| lint_noteB | Validates a note against its resolved schema. Pass |
| validate_folderA | Classifies and validates a folder. Pass |
| validate_areaA | Recursively validates a subtree. Pass |
| validate_allA | Validates the entire directory tree using the convention cascade. Optional |
| list_schemasA | Lists all loaded schemas. No arguments. Returns |
| create_noteA | Creates a new note with convention-aware defaults. Pass |
| get_backlinksA | Finds all notes linking to a given note. Pass |
| find_unlinked_mentionsA | Finds plain-text occurrences of a note's title that are not wikilinked. Pass |
| find_broken_linksA | Finds wikilinks pointing to non-existent notes. Optional |
| find_orphansA | Finds notes with no incoming wikilinks. Optional |
| find_bidirectional_mentionsA | Two-direction mention sweep for batch new-note operations. Pass |
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 24 tools
Each tool has a clearly distinct purpose with detailed descriptions that eliminate ambiguity. For example, create_note and write_note both write notes but are differentiated by creation-only vs. overwrite/append/prepend modes. Similarly, the validation tools operate at different scopes (note, folder, area, all).
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_note, find_orphans, validate_all). No mixing of conventions like camelCase, and the pattern is predictable across all tools.
With 24 tools, the set covers a comprehensive range of operations for a note-taking system without feeling excessive. Each tool has a clear role, from basic CRUD to advanced link analysis and validation, justifying the count.
The tool surface covers the full lifecycle of note management: creation, reading, updating, deletion, moving, patching, frontmatter manipulation, linting, validation, search, tag management, link analysis, and directory navigation. No obvious gaps for the stated purpose.