Skip to main content
Glama

Calculate legacy Florida or Kansas supplier deadlines

calculate_supplier_deadlines

Legacy calculator for Florida and Kansas private projects. Calculates a material supplier's preliminary notice and lien filing deadlines from delivery events (contract supplier-events-v2), for questions that need deadline dates. Available baselines cover Florida and Kansas private projects; other states and public projects return review_required, which is a valid result, not an error. How the parameters depend on each other: last_delivery_date is required when deliveries_complete is true. Florida (FL) takes florida_final_payment_status and florida_termination_status; Kansas (KS) takes kansas_extension_status; these are rejected for other states. Each takes yes, no or unknown: an omitted or unknown answer keeps the affected deadline under review, and a blanket review flag is not accepted. The Florida final-payment answer holds the notice for suppliers not hired by the owner. A Florida event date is accepted only with the matching yes answer. Delivery dates are furnishing dates, not invoice dates. Returns JSON with an overall status (calculated or review_required), preliminary_notice and lien_filing (each with its own status: calculated, not_required, review_required or awaiting_final_delivery, plus deadline, days_from_now, description and statute source_url), critical_warnings, statute_citations, an exact echo of the submitted inputs and a disclaimer. Invalid or contradictory facts return an error naming the field before any API call. Requires a customer key and consumes one plan calculation unit. No project is saved, notice sent or lien filed. 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>",
      "first_delivery_date": "<first_delivery_date>",
      "project_type": "<project_type>",
      "hired_by": "<hired_by>",
      "deliveries_complete": "<deliveries_complete>",
      "context": "<context>"
    },
    "name": "calculate_supplier_deadlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesTwo-letter code of the state where the project is located, e.g. "FL", "KS", "TX"; any state or DC is accepted. Decides which event questions apply.
contextYesFor anonymous analytics, use one of these exact goals. Determine supplier notice and lien deadlines / Identify which facts a supplier calculation needs / Read a state's lien guide / Browse available lien guides. Leave empty if none fits. Keep personal and project information out of this field.
hired_byYesWho ordered the materials from the supplier: the owner, a contractor or a subcontractor.
project_typeYesPrivate commercial, private residential, or public (public projects always need review).
last_delivery_dateNoDate of the final delivery, YYYY-MM-DD, not earlier than first_delivery_date. Required when deliveries_complete is true.
deliveries_completeYestrue when the final delivery has happened (then last_delivery_date is required); false while deliveries are ongoing, which returns awaiting_final_delivery for the lien date.
first_delivery_dateYesDate materials were first delivered (first furnishing), YYYY-MM-DD. Not an invoice date.
kansas_extension_statusNoKansas only: was a statutory lien-period extension filed and mailed? no permits the ordinary lien baseline; yes, unknown or omitted requires qualified review.
florida_termination_dateNoFlorida only: contract or notice-of-commencement termination date, YYYY-MM-DD, not earlier than first_delivery_date. Supply only with florida_termination_status=yes; a lien date still requires qualified review.
florida_final_payment_dateNoFlorida only: owner final-payment date, YYYY-MM-DD, not earlier than first_delivery_date. Supply only with florida_final_payment_status=yes.
florida_termination_statusNoFlorida only: was the original contract or notice of commencement terminated? no permits the lien baseline; yes, unknown or omitted requires qualified lien review.
florida_final_payment_statusNoFlorida only: did the owner make final payment to the contractor? unknown when not verified. For suppliers not hired by the owner, unknown, omitted, or yes without florida_final_payment_date makes preliminary notice review_required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed2 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "For anonymous analytics, use one of these exact goals. Determine supplier notice and lien deadlines / Identify which facts a supplier calculation needs / Read a state's lien guide / Browse available lien guides. Leave empty if none fits. Keep personal and project information out of this field.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "state",
      -  "first_delivery_date",
      -  "project_type",
      -  "hired_by",
      -  "deliveries_complete"
      -]New value: +[
      +  "state",
      +  "first_delivery_date",
      +  "project_type",
      +  "hired_by",
      +  "deliveries_complete",
      +  "context"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / florida_final_payment_status / description
      Previous value: -"Florida only: did the owner make final payment to the contractor? unknown when not verified; omitted or unknown keeps the notice under review, and yes needs florida_final_payment_date for a notice baseline."New value: +"Florida only: did the owner make final payment to the contractor? unknown when not verified. For suppliers not hired by the owner, unknown, omitted, or yes without florida_final_payment_date makes preliminary notice review_required."
  4. Changed1 schema field changed
    • changedInput schema / properties / florida_final_payment_status / description
      Previous value: -"Florida only: did the owner make final payment to the contractor? Use unknown if unverified; omitted or unknown keeps the notice under review, and yes needs florida_final_payment_date for a notice baseline."New value: +"Florida only: did the owner make final payment to the contractor? unknown when not verified; omitted or unknown keeps the notice under review, and yes needs florida_final_payment_date for a notice baseline."
  5. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations flag a non-read-only, open-world, non-idempotent call, and the description adds substantial behavior beyond that: it requires a customer key, consumes one plan calculation unit, validates facts before the API call, and explicitly states no project is saved, no notice sent and no lien filed. This clearly explains why the call is not read-only, so there is no annotation contradiction, though the 'legacy' deprecation posture is only implied rather than stated.

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?

Front-loads purpose, then constraints, then the return shape and side effects, which suits a 12-parameter conditional tool. It is dense and slightly repetitive with the schema's own descriptions, but no sentence is filler given the conditional logic.

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 carries the full return contract: overall status values, per-deadline statuses including awaiting_final_delivery, deadline/days_from_now/source_url fields, warnings, citations, input echo and disclaimer. Combined with the error behavior and unit consumption, an agent has everything needed to call and interpret it.

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 coverage is 100%, so the baseline is 3, and the description earns an extra point by summarizing cross-parameter dependencies: last_delivery_date required when deliveries_complete is true, state-gated parameters rejected for other states, and the Florida final-payment answer suppressing notice for suppliers not hired by the owner. Much of this restates the schema, but the consolidated dependency rules add navigable meaning across 12 parameters.

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?

Opening sentence names a specific verb and resource (calculates a material supplier's preliminary notice and lien filing deadlines) and scopes it to Florida/Kansas private projects. 'Legacy calculator' hints at a distinction from calculate_supplier_deadlines_v3, but never states the difference explicitly, so an agent must infer which version to pick.

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

Usage Guidelines4/5

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

Gives clear when-to-use ('for questions that need deadline dates') and when-not ('other states and public projects return review_required, which is a valid result, not an error'), plus data-source scoping to contract supplier-events-v2. It stops short of naming a preferred alternative when the legacy baseline doesn't fit, despite a v3 sibling existing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.