doc-splitter
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOC_SPLITTER_PYTHON | No | Path to the Python interpreter for the ducsplit Python CLI. Defaults to python3. |
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 |
|---|---|
| split_documentC | Parse a PDF/DOCX and start the boundary planning session. |
| get_boundary_contextB | Return content window and safe cut candidates for the host agent. |
| commit_boundaryC | Commit a conceptual boundary cut or window extension. |
| write_chunksA | Write chunk markdown files and run verification after boundaries are complete. |
| get_chunkA | Read chunk content by numeric id (Markdown or extracted PDF text). |
| verify_integrityB | Run coverage, word-count, and table/image integrity checks. |
| get_chunk_analysis_contextB | Return full chunk content for host-agent conceptual analysis. |
| commit_chunk_analysisC | Store bilingual topic, study focus, and coherence flag for a chunk. |
| get_study_index_contextB | Return verified chunk metadata and analyses so the host agent can author the study indexes. |
| commit_study_indexC | Store Persian and English study indexes authored by the host agent. |
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 10 tools
Tool purposes are mostly distinct, but there is some potential confusion between 'commit_boundary' and 'commit_chunk_analysis' (both commit operations) and between 'get_boundary_context' and 'get_chunk_analysis_context' (both get context). However, descriptions clearly differentiate them based on what is being committed or retrieved.
All tools follow a consistent verb_noun pattern using snake_case: commit_*, get_*, split_document, verify_integrity, write_chunks. The naming is predictable and clear.
With 10 tools, the server is well-scoped for a document splitting workflow. Each tool serves a distinct stage in the process, from parsing to writing chunks, without unnecessary overlap.
The tool set covers the full lifecycle of document splitting: parsing, boundary context, committing boundaries, chunk retrieval, analysis, writing, verification, and study indexing. No obvious gaps are present.