Loading ToolBench
MCP server for rapid, lightweight conversion of various document formats to markdown for LLMs, with document manipulation, search, and diff capabilities
Server provides 7 tools with complete input schemas and descriptions. Naming follows verb_noun convention (read_, save_, edit_, search_, diff_, get_, list_). Descriptions are present and substantive (avg ~120 chars), exceeding the 10-char minimum. However, output schemas are not documented in the provided source, critical for LLM planning. Parameter descriptions are adequate but lack constraint details (ranges, formats, examples). Error handling guidance is absent. No tool annotations (readOnlyHint/destructiveHint) despite clear risk profiles. Composition is sound: tools are single-purpose and chainable (e.g., search_documents → read_document). Security: write tools (save_document, edit_document) lack permission gates or dry-run patterns.
Compare two documents and return unified or JSON diff output
Apply a batch of atomic edits to a document at the AST level and write back to disk in place
Extract and return the hierarchical outline (table of contents) of a document
List files in the workspace (read allowlist directories)
Read a document (file path, data URI, base64, or plain text) and convert it to markdown with embedded images
Convert markdown content to a target format and save to disk
Search documents using keyword (BM25) or grep mode with optional persistent index
Output schemas not documented. LLMs cannot plan downstream tool calls or extract required fields (e.g., does search_documents return file paths, content snippets, or both?). Baseline: 100% of A+ tools document return types.
Missing tool annotations (readOnlyHint, destructiveHint, idempotentHint). save_document_from_markdown and edit_document are destructive writes but lack destructiveHint. Agents cannot distinguish safe from risky operations.
Parameter constraints lack detail. search_documents accepts 'top_k' (integer) but no min/max bounds stated. edit_document accepts 'edits' (array) but structure of edit objects not documented. Baseline: 94% of A+ tools include format/range constraints in descriptions.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | 2026-07-28+ | v2 |
No error recovery guidance. Tools lack descriptions of failure modes or recovery steps. E.g., read_document_as_markdown may fail on unsupported formats, but no guidance on what to try next.
Destructive operations lack confirmation/dry-run pattern. save_document_from_markdown and edit_document modify disk state irreversibly. No mention of preview, dry-run, or confirmation step to prevent accidental data loss.