Loading ToolBench
MCPB Desktop Extension for drafting Motor Accident Claims Tribunal pleadings under the MV Act 1988 (2019 amended) across India. Provides 10 case types + 8 State exemplars with privacy firewall and anti-hallucination verification.
Server has 10 tools with clear naming (verb_noun pattern) and detailed descriptions (100-300 chars each). All tools have input schemas with type definitions. However, output schemas are entirely undocumented, no return type specifications visible in code. Parameter descriptions are present but lack constraint details (enums, ranges, formats). Error handling is minimal; no recovery guidance or actionable error messages. Tool composition is sound (single responsibility), but missing pagination/limits for list operations and no idempotent hints despite write operations.
Create a case folder for a given case type. Returns the absolute path to the case folder. This folder is used to store all artifacts (case-facts.md, drafts, verification reports, etc.) throughout the drafting pipeline.
Get the instructions for the drafting pipeline. Returns the persona and detailed instructions for one of the six agents: reader (privacy firewall), format (placeholder mapping), drafter (first draft), verifier (anti-hallucination), refiner (polish), or overseer (opposing-counsel lens).
Get the drafting format SKILL.md for a given case type. Returns the full SKILL.md content for the case type, including statutory anchors, format placeholders, and the drafting checklist. Also appends format-from-user.md if present in the same skill folder.
Get the complete step-by-step orchestration script for the full MACT drafting pipeline. Returns detailed instructions for executing all 10 steps from case folder creation through final draft production, including tool invocation order, artifact naming conventions, and falsification checks.
Get the universal pleading skeleton and common drafting discipline (citation rules, AI-fabricated-citation risk per HC cautions). This is the foundational template used across all case types.
No output schemas documented. Tools return complex objects (dicts, markdown content, file paths) but LLMs have no specification of return fields, types, or structure. Forces LLMs to infer output shape from descriptions alone.
Parameter constraints missing. 'case_type' and 'state' accept enums but descriptions lack explicit enum lists. 'agent_name' defaults to empty string with no validation guidance. LLMs cannot self-correct invalid values.
No error handling or recovery guidance. Tools may fail (file I/O, pandoc conversion, invalid paths) but descriptions provide no error classification, retry logic, or actionable recovery steps.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 59 | 2026-07-28+ | v2 |
Get the state-specific configuration and exemplar pleading for a given state. Returns the full markdown content including state-specific MACT bench details, procedural variations, and exemplar pleading structure.
List all case types this connector can draft. Returns a dict with the list of case types, a short description of each, AND an acronym disambiguation map (Indian advocacy acronyms / Form references / statutory section references -> case_type). CRITICAL: the user's acronym IS the source of truth for case_type classification. Do not infer case_type from input-document content.
List all available state exemplars for MACT drafting. Returns a sorted list of state codes/names for which state-specific configuration and exemplar pleadings are available.
Save a text artifact (markdown, plain text, etc.) to disk within a case folder. Creates parent directories as needed. Used to persist outputs from each agent in the pipeline (case-facts.md, format-shell.md, verification-report.md, opposing-notes.md, final-draft.md, etc.).
Convert a markdown draft to a Word .docx file using pandoc and the reference.docx template. Applies locked Word styles (TNR 14pt, 1.5 spacing, justified, Bombay HC formatting conventions) and fixes table column widths post-pandoc. Used to produce filing-grade .docx outputs from markdown drafts.
Write operations lack idempotent hints and confirmation patterns. 'save_artifact' and 'save_draft_as_docx' can overwrite files silently. No dry-run, confirmation, or idempotent markers to prevent accidental data loss.
List operations lack pagination. 'list_case_types' and 'list_states' return unbounded arrays with no limit, offset, or cursor parameters. Violates pattern for scalable result handling.