maharashtra-courts-drafting
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_case_typesA | List instruments this connector can draft for Maharashtra forums. |
| get_case_type_formatA | Return the long-form template + skill + user-facts checklist for one instrument. Load order: official template first, then short skill note, then common rules, then Index/Synopsis sheets for High Court filings. |
| get_agent_instructionsA | Mandatory first call with no arguments returns the orchestration script. Pass reader / format / drafter / verifier / refiner / overseer for one persona. |
| get_pleading_baseB | Shared Maharashtra pleading skeleton. |
| list_forumsA | List Bombay benches and Maharashtra tribunal forum-configs. |
| get_forum_configB | Return the forum-config exemplar (header, separator, annexure, paper). |
| resolve_benchB | Map a Maharashtra district to the correct Bombay bench, MAT bench or DRT. forum_family: high-court | mat | drt | mact | consumer Kolhapur-circuit districts: confirm the circuit is sitting that week; otherwise file at the Principal Seat. |
| create_case_folderC | Create inputs/ and artifacts/ under Downloads/MH-Courts-Drafts (or root). |
| save_artifactA | Save an allow-listed pipeline artifact into the case folder. |
| read_case_folderB | Read md / txt / pdf / docx under inputs/ and artifacts/. |
| save_draft_as_docxC | Render a markdown draft to a filing-grade docx via pandoc. |
| list_templatesA | List every official long-form template packed with this connector. |
| get_templateA | Return a long-form template by case_type key or by relative path. Examples: civil-wp, wp-reply-affidavit, high-court/civil-writ-petition.md |
| get_reference_noteA | Load a packed reference. Names: getting-started, harness, territorial-jurisdiction, acronyms, court-fees-stamp, efiling. Also accepts docs/INSTALL or docs/HARNESS. |
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 14 tools
Most tools have clearly separated responsibilities (forum resolution, folder management, template retrieval), but get_template and get_case_type_format overlap because both can return a long-form template, and list_templates vs list_case_types are similar catalogues. The descriptions reduce ambiguity but an agent may need to read carefully to pick the right one.
All tools follow a consistent verb_noun snake_case convention (list_*, get_*, create_*, save_*, read_*, resolve_*), and the object after the verb is specific. This makes the set predictable and easy to navigate.
14 tools is at the upper edge of the ideal range, but each tool addresses a distinct stage of the drafting workflow (jurisdiction, folder setup, template loading, rendering). A few meta/utility tools (get_agent_instructions, get_reference_note) add weight but are justifiable.
The surface covers the main drafting lifecycle: resolve forum, create/read case folder, load templates/case formats, and render a DOCX. Missing capabilities like validation, final bundle assembly, or e-filing are notable but can be worked around by the agent/refiner.