lease-qa-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LEASECLEAR_BASE_URL | Yes | Base URL of a running LeaseClear API (e.g. http://localhost:8001) |
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 |
|---|---|
| lease_qaA | Ask one neutral, precise question about the tenant's lease. The lease document is already scoped for this email. Returns an answer grounded in the lease, or states that the lease does not address the question. |
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 1 tool
With only one tool, there is no possibility of confusion or overlap. The tool's purpose is clear and unique.
A single tool name cannot be inconsistent with others. The name 'lease_qa' is straightforward and matches the server's purpose.
Having only one tool feels thin for a typical server, but it may be appropriate for this narrow scope. The calibration suggests 1-2 tools is borderline.
The tool directly fulfills the stated purpose of asking lease questions and getting grounded answers. Minor gaps exist, such as no ability to retrieve the full lease or ask multiple questions in a batch, but the core workflow is covered.