Skip to main content
Glama

Get the lien guide for one state

get_state_lien_guide
Read-onlyIdempotent

Returns LienDeadline's editorial mechanics lien and preliminary notice guide for one state or DC: rules (rule summary with statute citations), deadline_rows (deadline table), faqs (common questions) and source_url (the guide's web page), roughly 4 KB of JSON. For questions about how a state's lien or notice rules work, why a deadline falls where it does, or which statute applies. An unknown state code returns an error. The guide is an editorial reference, not a calculation: its day counts are summaries, not computed deadlines. Public and read-only; no key needed.

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>",
      "context": "<context>"
    },
    "name": "get_state_lien_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesTwo-letter US state or DC code, e.g. "TX"; case-insensitive.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
      -]New value: +[
      +  "state",
      +  "context"
      +]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description adds real value on top: payload size (~4 KB JSON), error behavior for unknown state codes, and the crucial caveat that day counts are editorial summaries and not computed deadlines. 'No key needed' is largely redundant with the public/read-only annotations.

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-loaded with the return shape, then use cases, then caveats and access notes; no filler sentences. The closing 'Public and read-only; no key needed' partly restates the annotations and could be trimmed.

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 does the work by naming the four returned fields and their meaning, plus error behavior and the editorial caveat. For a two-parameter read tool, nothing an agent needs in order to call it correctly is missing.

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 both parameters are already documented in the schema. The description adds only the error behavior for an invalid state code and says nothing about the analytics 'context' parameter, which is where an agent would most benefit from guidance. Baseline 3 is appropriate when the schema carries the semantics.

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

Purpose5/5

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

Specific verb and resource ('Returns LienDeadline's editorial mechanics lien and preliminary notice guide for one state or DC') followed by an enumeration of the returned fields (rules, deadline_rows, faqs, source_url). An agent can distinguish this from the calculate_* siblings because the description explicitly frames it as an editorial reference rather than a computation.

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 explicit when-to-use conditions: rules questions, why a deadline falls where it does, which statute applies. It also implicitly routes calculation work elsewhere ('not a calculation: its day counts are summaries, not computed deadlines'), though it never names calculate_supplier_deadlines or list_state_lien_guides as the alternatives.

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.