Loading ToolBench
MCP server for AiDocX - Create, upload, and manage documents and presentation decks from AI assistants
Mixed quality across 15 tools. All tools have descriptions and explicit schema definitions, which is strong. However, descriptions vary significantly in clarity and actionability, some are excellent (create_document with explicit supported types, analysis caveats), others lack key details (delete_document, delete_folder lack specificity on confirmation behavior). Parameter descriptions are generally present but sometimes generic. Most tools accept UUID identifiers without offering human-friendly alternatives, increasing lookup burden. Error handling is partially visible in api-client.ts but not consistently integrated into tool responses. Schema definitions use proper JSON Schema with enums (documentType, theme, sortBy, sortOrder) and type constraints, which supports constrained input well. Composition is good, tools chain logically (search → get → analyze/edit → delete). Pagination is present on list/search tools with limit/offset patterns, though some tools lack explicit result count fields in documented schemas. Critical gap: no visible tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite destructive operations existing.
Analyze a document using AI. For contracts, returns a risk score (0-100), key clauses, and missing protections. For other document types, returns a summary and improvement suggestions. NOTE: This operation consumes AI tokens from the user's subscription plan. The analysis may take 10-30 seconds depending on document length.
Create a presentation deck from text content using AI. Provide raw text (article, report, meeting notes, data) and AI will automatically generate a multi-slide presentation with professional layout, typography, and design. The generated deck includes: - Cover slide with title and date - Content slides with cards, quotes, bullet points - Summary slide with key takeaways - Consistent color theme and typography Supports dark and light themes. Each slide is 1280×720px (16:9). Use cases: - Convert blog posts or articles into presentation decks - Generate IR (Investor Relations) decks from company data - Create trend briefings from research notes - Turn meeting minutes into shareable slide summaries
Create a new document in AiDocX. The content is rendered to a professionally formatted PDF (A4, proper margins) and stored in document management. Supported document types: - contract: Contracts, NDAs, employment agreements, service agreements - proposal: Project proposals, consulting proposals - quotation: Price quotes, cost estimates, invoices - plan: Project plans, strategy documents - business-plan: Investor pitch business plans, startup plans - business-trip-plan: Travel plans with itinerary and budget - business-trip-report: Post-trip reports with outcomes and expenses - report: Analysis reports, audit reports, due diligence - official-letter: Official letters, notices, requests - resume: Resumes, CVs, cover letters - purchase-order: Purchase orders, delivery notes, invoices - manual: SOPs, user manuals, guides IMPORTANT: Before calling this tool, you MUST confirm the following with the user: 1. Document type (e.g., contract, quotation, resume, proposal) 2. Key details (parties, terms, items, or sections depending on type) 3. Any special requirements or clauses Generate professional, well-structured HTML appropriate for the document type. Do NOT include <html>/<head>/<body> wrapper — only the inner content. - Contracts: include signature blocks at the bottom - Quotations: include item tables with totals - Resumes: include profile, experience, education sections - Proposals: include executive summary, scope, timeline, pricing
Missing tool annotations (readOnlyHint, destructiveHint, idempotentHint) for destructive operations (delete_document, delete_folder, delete_deck). LLM cannot distinguish read-only tools from destructive ones without explicit hints.
Delete tools (delete_document, delete_folder, delete_deck) lack explicit confirmation/dry-run support in schema. Descriptions mention 'confirm with user' but tool design offers no programmatic gate (dry_run param, result with confirmation required). Pattern:confirmation-request suggests implementing reversible ops.
All tools accept only UUID identifiers (id, folderId) without accepting human-friendly names or emails. Users must call search/list first to obtain IDs, forcing multi-step agent planning. Pattern:natural-identifiers recommends accepting names alongside IDs.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | C | 60 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 47 | - | v1 |
Create a new folder in AiDocX document management.
Delete a presentation deck from AiDocX. This action is irreversible. IMPORTANT: Always confirm with the user before deleting a deck. This will permanently remove the deck and all its slide designs.
Delete a document from AiDocX document management. This action is irreversible. IMPORTANT: Always confirm with the user before deleting a document.
Delete a folder from AiDocX document management. IMPORTANT: Always confirm with the user before deleting. Use recursive=true only when the user explicitly wants to delete all contents.
Edit a presentation deck's metadata or slide design. Can update: - Deck name (title) - Move to a different folder - Full slide design (components JSON) For design updates, provide the complete pages array. Each page contains: - theme: { background, fontFamily, accentColor } - components: array of text, shape, icon, or table components with coordinates IMPORTANT: To edit design, first use get_deck to retrieve the current design, modify the specific parts, then send the full updated design back.
Get details of a specific presentation deck, including its slide design data. Returns deck metadata (name, type, status) and the full design JSON (slide components, themes, layout). Use this to inspect deck contents before editing.
Get details of a specific document in AiDocX. Returns name, type, labels, size, and extracted text content.
List presentation decks in the user's AiDocX account. Returns deck ID, name, type, status, creation date, and folder info. Supports filtering by folder and pagination.
List documents in the user's AiDocX document management. Returns all document types (contracts, proposals, quotations, resumes, reports, etc.). Supports pagination.
List folders in the user's AiDocX document management.
Search documents in AiDocX. Searches across all document types (contracts, proposals, quotations, resumes, reports, etc.). Supports text search, date filtering, and pagination. Returns matching documents sorted by relevance by default.
Upload a PDF or Office document (DOC, DOCX, HWP, XLS, XLSX, PPT, PPTX) to AiDocX. Office files are auto-converted to PDF. Works for any document type: contracts, proposals, quotations, resumes, reports, etc.
List/search tools (list_documents, list_decks, search_documents) document limit/offset but do not explicitly document output structure including total count or next_cursor. Pagination guidance missing.
Error handling visible in api-client.ts (401, 402, 403, 404, 413, 429 with recovery hints) but tool-level error responses not documented in tool schemas. LLM cannot see which errors are retryable vs fatal.
create_document and create_deck descriptions mention AI token consumption but no explicit cost/quota parameter or preview mode. LLM cannot estimate cost before execution.
edit_deck schema requires 'complete pages array' for design updates but does not document what fields are required vs optional within each page/component object. LLM must infer schema from example.