liendeadline-mcp
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| calculate_lien_deadlineA | Calculates the preliminary notice deadline and the lien filing deadline for a US construction invoice. Needs the invoice or delivery date and the state. Returns dates, days remaining, and any warnings such as weekend or holiday rollover. Covers all 50 states plus DC. Not legal advice. |
| list_supported_statesA | Returns the two-letter codes of every US jurisdiction with deadline rules available, all 50 states plus DC. Use this to check a code before calculating. |
| get_state_lien_guideA | Returns the underlying deadline rules for a state, including statute citations, the deadline table and common questions. Use this when the user asks why a deadline falls where it does, or wants the statute, rather than just a date. |
| list_state_lien_guidesA | Returns every available state guide with its code, title and slug. Useful for discovering what exists before fetching one. |
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 has a clearly defined role: calculating a deadline, checking supported states, and interacting with state guides. The only minor ambiguity is between list_supported_states and list_state_lien_guides, since both enumerate states, but their purposes are distinct enough for an agent to choose correctly.
All tool names follow a consistent verb_noun snake_case pattern: calculate_, list_, get_, list_. The verbs and nouns are descriptive and match the tool's function, making the set predictable and easy to navigate.
Four tools is well-scoped for this focused domain. Each tool serves a necessary purpose: one core calculation, one validation lookup, and two guide discovery/retrieval operations. Nothing feels redundant or missing at this level of granularity.
The domain is construction lien deadline calculation, and the tool set covers the full workflow: verify state support, calculate the deadline, retrieve detailed rules, and discover available guides. There are no obvious dead ends, and the stateless nature of the domain does not require update or delete operations.