pactlio-mcp
OfficialServer 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_contract_typesA | List all contract and legal document types Pactlio can generate, with descriptions, use cases, and USD prices. Start here to find the right contract type slug/id for other tools. |
| get_jurisdiction_requirementsA | Statute-cited legal requirements, key differences, common pitfalls, terminology, and FAQs for a contract type in a specific US state or country. Use contract slug (e.g. "contractor-agreement") + jurisdiction slug (e.g. "california", "us", "uk", "eu-gdpr"). |
| check_non_compete_enforceabilityA | Whether a non-compete agreement is enforceable, limited, or void in a given US state (or DC), with salary thresholds and the key statute. Data covers all 50 states + DC. |
| get_intake_questionsA | The questions Pactlio asks to draft a specific contract type — use these to collect the information needed before calling start_contract_draft. Returns fields, types, options, and validation rules. |
| start_contract_draftA | Start generating a contract draft with Pactlio's multi-agent AI engine (drafter, critic, compliance checker). Takes 3-5 minutes — returns a preview_id immediately; poll get_draft_status. Free preview shows the opening sections; the full contract is unlocked by a human via checkout. Provide deal_summary fields collected via get_intake_questions (at minimum: parties, plus the required fields for the contract type). |
| get_draft_statusA | Check a contract draft started with start_contract_draft. While generating returns status "pending". When complete, returns the free preview (opening sections), the titles of locked sections, and the URL where a human can pay to unlock the full contract. |
| get_checkout_linkA | Returns the URL where a human can view the preview and pay to unlock the full contract for a draft created with start_contract_draft. Share this link with your user. |
| analyze_contractA | Paste contract text and get an AI risk analysis: red flags, one-sided clauses, missing protections, and questions to ask. Free (2/day). Not legal advice. |
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 8 tools
Each tool targets a distinct aspect of contract drafting and analysis: analyzing existing contracts, checking non-compete enforceability, managing drafts (start, status, checkout), and retrieving reference data (intake questions, jurisdiction requirements, contract types). No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (e.g., analyze_contract, get_draft_status, start_contract_draft). The naming is predictable and uses snake_case uniformly, making it easy for agents to understand the action and target.
With 8 tools, the server is well-scoped for its purpose of contract drafting and legal analysis. Each tool serves a clear function without redundancy, and the count is neither too sparse nor overwhelming.
The tool set covers the core workflow (list types, get intake questions, start draft, check status, get checkout link) and adds analytical capabilities. However, there is no tool to retrieve the full contract text after payment, which may require manual intervention, slightly limiting end-to-end automation.