Skip to main content
Glama
liendeadline-mcp

liendeadline-mcp

Calculate invoice deadlines (customer API key)

calculate_lien_deadline

Calculate preliminary notice and lien filing deadlines from a construction invoice date and US state, returning deadline dates, day counts, waiver due date, and rollover warnings.

Instructions

Customer API tool: requires LIENDEADLINE_API_KEY, a dedicated LienDeadline customer key; without one it returns a configuration error and makes no request. Calculates the preliminary notice and lien filing deadlines for one construction invoice from its invoice or delivery date and state. Returns JSON with state, invoice_date, project_type, preliminary_notice_deadline, lien_deadline, waiver_due_date, prelim_deadline_days, lien_deadline_days, warnings such as weekend or holiday rollover, notes and a disclaimer. A date, day count or project_type the API does not return is null; missing warnings is [] and missing notes is an empty string. API denials (401 key, 403 scope, 429 rate limit) return a tool error. Successful calculations consume one API plan unit. Not legal advice.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "state": "<state>",
      "invoice_date": "<invoice_date>"
    },
    "name": "calculate_lien_deadline"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoYour role on the project, e.g. "supplier", "contractor", "subcontractor".
stateYesTwo-letter US state code, e.g. "TX", "CA", "DC", from the jurisdictions the customer API supports.
notice_dateNoNotice of completion date in YYYY-MM-DD format, if known; not the date a preliminary notice was sent. Omit otherwise.
invoice_dateYesInvoice or delivery date in YYYY-MM-DD format; deadlines count from it.
project_typeNo"commercial" or "residential" (case-insensitive). Omit for commercial. Changes the deadline in some states.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.11
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed2 schema fields changedv0.5.8
    • changedInput schema / properties / notice_date / description
      Previous value: -"Date a preliminary notice was actually sent, YYYY-MM-DD, if one was. Omit otherwise."New value: +"Notice of completion date in YYYY-MM-DD format, if known; not the date a preliminary notice was sent. Omit otherwise."
    • changedInput schema / properties / project_type / description
      Previous value: -"Usually \"Commercial\" or \"Residential\". Changes the deadline in some states."New value: +"\"commercial\" or \"residential\" (case-insensitive). Omit for commercial. Changes the deadline in some states."
  3. Changed1 schema field changedv0.5.4
    • changedInput schema / properties / state / description
      Previous value: -"Two-letter US state code, e.g. \"TX\", \"CA\", \"DC\"; one of the codes list_supported_states returns."New value: +"Two-letter US state code, e.g. \"TX\", \"CA\", \"DC\", from the jurisdictions the customer API supports."
  4. Changed4 schema fields changedv0.3.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / invoice_date / description
      Previous value: -"Invoice or delivery date in YYYY-MM-DD format."New value: +"Invoice or delivery date in YYYY-MM-DD format; deadlines count from it."
    • changedInput schema / properties / notice_date / description
      Previous value: -"Date a preliminary notice was actually sent, YYYY-MM-DD, if one was."New value: +"Date a preliminary notice was actually sent, YYYY-MM-DD, if one was. Omit otherwise."
    • changedInput schema / properties / state / description
      Previous value: -"Two-letter US state code, e.g. \"TX\", \"CA\", \"DC\"."New value: +"Two-letter US state code, e.g. \"TX\", \"CA\", \"DC\"; one of the codes list_supported_states returns."
  5. First observedv0.1.0

TDQS

A4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations, the description discloses the required API key and the failure mode without one, HTTP denial handling (401/403/429), the billing unit consumed per successful call, and the null/empty-string/empty-array semantics of missing fields. It also disclaims 'Not legal advice,' giving the agent a clear picture of side effects and limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense but efficient: the auth requirement is front-loaded and most sentences carry distinct information (return fields, null semantics, error codes, billing). The lack of paragraph breaks or bullets for the long return-field list is the main minor weakness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by enumerating the returned JSON fields, warning behavior, null/missing-value conventions, and error codes. An agent has everything needed to call it, interpret results, and anticipate failures.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents every parameter including role, notice_date, and project_type defaults. The description only restates that deadlines derive from invoice or delivery date and state, adding little meaning beyond the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it 'Calculates the preliminary notice and lien filing deadlines for one construction invoice from its invoice or delivery date and state.' The 'Customer API tool' framing plus the dedicated key name partially differentiates it from the supplier-deadline siblings, though it never explicitly contrasts with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied (one construction invoice, keyed by state and invoice date) and the auth precondition is stated, but there is no explicit when-to-use/when-not guidance or routing to the sibling calculate_supplier_deadlines tools for other key types.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.