Skip to main content
Glama

List all state guides

list_state_lien_guides
Read-onlyIdempotent

Lists every published state lien guide in one response, without pagination: count plus state_code, title and slug for all 50 states and DC, in alphabetical order by state name. It lists editorial guides only and does not indicate which states have calculated deadlines. Takes no parameters. 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": {
      "context": "<context>"
    },
    "name": "list_state_lien_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
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"
      +}
    • addedInput schema / required
      Added value: +[
      +  "context"
      +]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description still adds real value: no pagination, everything in one response, alphabetical ordering, editorial-only content, and public/no-key access. It does not discuss rate limits or response size, but for a 51-row list that is minor.

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 what is returned and why it is complete in one call; the ordering and content-scope details follow logically. No filler sentences, though the false "Takes no parameters" clause occupies prime real estate with misinformation.

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

Completeness4/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 well by enumerating the returned fields (count, state_code, title, slug) and ordering. Access requirements and the editorial-only limitation are covered. The only shortfall is the inaccurate claim of zero parameters, which is exactly the kind of detail an agent needs correct before calling.

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

Parameters2/5

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

The schema documents its single required "context" parameter at 100% coverage with enumeration-style values, which would normally justify a 3. However, the description asserts "Takes no parameters," directly contradicting the schema's required field — an agent following the description could omit context and fail validation. This is a substantive parameter-level error rather than a mere gap.

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?

States a specific verb and resource ("Lists every published state lien guide") plus scope (all 50 states and DC, single response, no pagination). The contrast with get_state_lien_guide and with the deadline-calculation siblings is implicit but clear from "every published ... guide" versus a single-state lookup.

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 context for use — browsing the full catalog of guides — and signals an exclusion ("does not indicate which states have calculated deadlines"), which points an agent toward calculate_supplier_deadlines for deadline data. It stops short of naming that sibling explicitly, leaving the routing to inference.

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.