break-clause-analyzer
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | No | Anthropic API key for live LLM extraction (optional; without it, the server uses a heuristic baseline). |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract_break_clauseA | Extract the tenant break clause from a lease document, returning its verbatim text and source span (or found=false). Decision-support only. |
| check_conditionsA | Evaluate the four conditions precedent (notice timing, notice validity, rent/no-arrears, vacant possession) against the document, each pass/fail/uncertain with grounded evidence. Decision-support only. |
| find_citationA | Return the exact verbatim text in the source that supports a claim, or NOT_FOUND. Never invents text. Deterministic. Decision-support only. |
| assess_validityA | Orchestrated assessment: VALID / INVALID / AMBIGUOUS with per-condition results, the conditions that forced the verdict, a calibration note, and mandatory human-verify gates. Abstains to AMBIGUOUS rather than guess. Decision-support only. |
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 4 tools
Each tool targets a distinct step in the analysis pipeline: extract the clause, check conditions, find supporting evidence, and produce the final assessment. There is no overlap in purpose.
All tool names follow the verb_noun pattern (extract_break_clause, check_conditions, find_citation, assess_validity), making the naming scheme predictable and uniform.
With 4 tools, the server is well-scoped for a focused break-clause analysis workflow. Each tool serves a necessary, non-redundant role.
The tool set covers the full analysis lifecycle: extraction, condition evaluation, citation retrieval, and final validity assessment. No obvious dead ends or missing operations for the stated purpose.