Related Servers

The tool set contains multiple consolidated facades and direct tools that heavily overlap: document, document_asset, fetch_document_asset, section, docx, docx_table, and evidence all cover document/asset territory, while job duplicates get_job_status/list_jobs. Even with detailed descriptions, an agent must read long contracts to pick the right entrypoint. Several tools have unclear boundaries despite some well-written individual descriptions.

Names are consistently lowercase and snake_case, but they follow no single pattern: action-first names like ingest_documents and get_docx_content coexist with noun-only entrypoints like document, job, section, and evidence, plus the mixed table_manage/table_data versus plan_table style. Most names are readable and descriptive, but the generic single-word facades are vague and the overall convention is uneven.

30 tools exceeds the 25-tool threshold and is inflated by redundant consolidated/direct pairs, e.g., document vs document_asset vs docx, and job vs get_job_status/list_jobs. The underlying domain is broad, but many tools could be merged or removed without losing capability, making the surface feel heavy for agents to navigate.

The server covers the document lifecycle well: PDF/DOCX ingestion, document listing and asset retrieval, table CRUD/drafts/citations, evidence spans/bundles, DOCX write-back, and job tracking. Minor gaps remain, such as the lack of a clearly exposed direct PDF create/update/delete tool outside the monolithic document facade and no OCR path, but core workflows have no dead ends.