Skip to main content
Glama
liendeadline-mcp

liendeadline-mcp

Calculate supplier deadlines from confirmed project facts

calculate_supplier_deadlines_v3

Calculates supplier notice and mechanics lien deadlines from confirmed project facts and rule identities, returning sourced outcomes and flagging unresolved facts for qualified review.

Instructions

Evaluates confirmed supplier-events-v3 facts against the rule and question identities from v3 discovery. Returns separate sourced notice and lien outcomes, including qualified review when relevant facts are unresolved, and an exact nested input echo. When RI discovery asks ri_mailed_within_200_days after ri_mailed=yes, confirm whether mailing occurred within 200 days of first delivery. No, Unknown or omitted confirmation requires review; recording alone does not establish a 40-day target. Only calculated outcomes contain calculated deadline dates. Report every candidate_deadlines entry with its ID, date and sources under the API explanation. For NH review fallbacks, first_furnishing is a conservative checkpoint and final_furnishing is informational pending contract grouping and qualifying completion; passing the first checkpoint does not itself establish expiry. A calculated contract_completion outcome uses only the returned deadline, without substituting the first checkpoint or recomputing a date. Review candidates do not establish filing deadlines, completion or scheduled reminders. An optional preliminary_notice.notice_duties collection contains independently required named notices, each with its own calculated date, explanation and sources; the legacy preliminary date is only their earliest summary. Report every validated duty without inferring duties from candidates or treating one notice as satisfying all duties. A separate optional preliminary_notice.planned_notice_targets collection contains qualified intent planning targets with their target dates, assumed filing dates, full ten- or thirty-day intervals, explanations and sources. Planning targets do not establish statutory expirations, actual filing, notice completion or scheduled notifications. An optional verified action_by is a Conservative action date planning target under qualified review; the statutory deadline and countdown remain unresolved, with explanation, sources and warnings. Optional recurring_notice_facts supplies actual Tennessee furnished months or New Hampshire account records. Tennessee recurring_notice_periods cover entered periods only, including paid and unknown states; known unpaid duties remain independent. New Hampshire recurring_notice_checkpoints are advisory check-ins with unresolved legal status, not legal deadlines, service, completion or scheduled reminders; they do not reset earlier gaps. Never infer intervening months or blanket completion. Stale identities return 409, unavailable reviewed sources return 503. Requires a customer key and consumes one plan calculation unit. No project is saved, notice sent or lien filed.

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>",
      "project_type": "<project_type>",
      "hired_by": "<hired_by>",
      "rules_source": "<rules_source>",
      "questions_identity": "<questions_identity>",
      "events": "<events>"
    },
    "name": "calculate_supplier_deadlines_v3"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesProject jurisdiction: state or DC.
eventsYesDiscovered event IDs only; missing means unknown. Date only for yes and only where the question permits it. Invoice dates are not furnishing dates.
hired_byYesWho ordered the materials from the supplier: the owner, a contractor, or a subcontractor.
project_typeYesConstruction project type: private commercial, private residential, or public.
rules_sourceYesExact rules_source from discovery for this scope.
questions_identityYesExact questions_identity from discovery.
recurring_notice_factsNoOnly when discovery returns a matching recurring_notice_intake descriptor. Actual recurring facts only: Tennessee entered furnished months with unpaid and retainage-only answers, or New Hampshire actual written accounts with coverage and supplied dates. Omission retains legacy behavior; unknown answers require review. Do not infer intervening months or actual notice from a plan. NH actual owner notice belongs in the discovered nh_owner_notice_given event.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.5.11
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / hired_by / description
      Added value: +"Who ordered the materials from the supplier: the owner, a contractor, or a subcontractor."
    • addedInput schema / properties / project_type / description
      Added value: +"Construction project type: private commercial, private residential, or public."
  2. Changed1 schema field changedv0.5.5
    • addedInput schema / properties / recurring_notice_facts
      Added value: +{
      +  "description": "Only when discovery returns a matching recurring_notice_intake descriptor. Actual recurring facts only: Tennessee entered furnished months with unpaid and retainage-only answers, or New Hampshire actual written accounts with coverage and supplied dates. Omission retains legacy behavior; unknown answers require review. Do not infer intervening months or actual notice from a plan. NH actual owner notice belongs in the discovered nh_owner_notice_given event.",
      +  "oneOf": [
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "kind": {
      +          "const": "tn_monthly_nonpayment",
      +          "type": "string"
      +        },
      +        "months": {
      +          "items": {
      +            "additionalProperties": false,
      +            "properties": {
      +              "month": {
      +                "pattern": "^\\d{4}-(0[1-9]|1[0-2])$",
      +                "type": "string"
      +              },
      +              "retainage_only": {
      +                "enum": [
      +                  "yes",
      +                  "no",
      +                  "unknown"
      +                ],
      +                "type": "string"
      +              },
      +              "unpaid": {
      +                "enum": [
      +                  "yes",
      +                  "no",
      +                  "unknown"
      +                ],
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "month",
      +              "unpaid",
      +              "retainage_only"
      +            ],
      +            "type": "object"
      +          },
      +          "maxItems": 16,
      +          "minItems": 1,
      +          "type": "array"
      +        },
      +        "version": {
      +          "const": "supplier-recurring-facts-v1",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "version",
      +        "kind",
      +        "months"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "accounts": {
      +          "items": {
      +            "additionalProperties": false,
      +            "properties": {
      +              "covered_through": {
      +                "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      +                "type": "string"
      +              },
      +              "id": {
      +                "pattern": "^[a-z][a-z0-9_]{0,79}$",
      +                "type": "string"
      +              },
      +              "supplied_date": {
      +                "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "id",
      +              "covered_through",
      +              "supplied_date"
      +            ],
      +            "type": "object"
      +          },
      +          "maxItems": 16,
      +          "type": "array"
      +        },
      +        "kind": {
      +          "const": "nh_written_account",
      +          "type": "string"
      +        },
      +        "version": {
      +          "const": "supplier-recurring-facts-v1",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "version",
      +        "kind",
      +        "accounts"
      +      ],
      +      "type": "object"
      +    }
      +  ]
      +}
  3. Addedv0.5.4

TDQS

A3.9/5.0
Behavior5/5

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

The annotations already declare non-read-only, open-world, non-idempotent, and non-destructive behavior, and the description adds substantial context beyond them: it consumes one plan calculation unit, saves no project, sends no notice, files no lien, returns 409 for stale identities and 503 for unavailable reviewed sources, and distinguishes calculated outcomes from review candidates and planning targets. These disclosures are unusually thorough and do not contradict the annotations.

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

Conciseness2/5

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

The description is a dense wall of text with no paragraph breaks, bullets, or clear separation between input semantics, output semantics, and behavioral caveats. It repeats several warnings about review candidates, planning targets, and non-inference, which makes the definition harder to scan than its complexity alone would require.

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?

There is no output schema, so the description carries the full burden of explaining return values, and it does so extensively: separate notice and lien outcomes, qualified review, nested input echo, preliminary notice duties, planned notice targets, action_by, and recurring notice facts. It also covers authentication, billing consumption, error statuses, and side effects, making it complete enough for an agent to call the tool correctly.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema already carries the baseline parameter semantics. The description nevertheless adds meaningful conditional guidance for events, such as how ri_mailed_within_200_days should be confirmed after ri_mailed=yes and why omitted or unknown confirmation requires review, and it clarifies that recurring_notice_facts should be supplied only when discovery returns a matching descriptor with actual facts rather than inferred months.

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 evaluates confirmed supplier-events-v3 facts against rule and question identities from v3 discovery and returns sourced notice and lien outcomes. It is clearly not a generic calculator, but it does not explicitly distinguish itself from the sibling calculate_supplier_deadlines or explain when v3 versus the non-v3 tool should be used.

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 through prerequisites such as v3 discovery identities, confirmed facts, a customer key, and a matching recurring_notice_intake descriptor. However, it never explicitly says when to choose this tool over calculate_supplier_deadlines or calculate_lien_deadline, nor does it give a clear when-not statement.

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