Skip to main content
Glama
Sign In

Ucc Liens

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Ucc Search

ucc_search
Read-onlyIdempotent

Search UCC (Uniform Commercial Code) financing-statement filings by debtor business name, for Colorado, Connecticut or Oregon (each state's own public Secretary of State open-data portal). Business debtors only — individual debtors are excluded at the source query, never fetched. Oregon's result set covers a rolling ~30-day window; Vermont has no automatable source (its one public search is reCAPTCHA-gated) and returns a loud error, not an empty list. Not a consumer report. Not for use in credit, employment, insurance or housing eligibility decisions (FCRA).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "state": "CT",
      "debtor_name": "NPG Holdings"
    },
    "name": "ucc_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax filings to return (default 20, max 100).
stateYesTwo-letter state code: CO, CT, OR, or VT (VT always errors — see tool description).
debtor_nameYesBusiness debtor name (or fragment) to search for, e.g. "Green Mountain Coffee".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: individual debtors are filtered at the source query, Oregon returns only a rolling ~30-day window, and Vermont returns a loud error rather than an empty list. These are exactly the surprises that would otherwise mislead an agent interpreting results.

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?

The purpose and scope are front-loaded, and each clause carries distinct information (state coverage, source filtering, Oregon window, VT failure mode, FCRA limits). It is dense and parenthetical-heavy, but nothing is filler.

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 should ideally sketch the returned filing fields, which it does not; an agent knows what it can ask for but not what comes back. Everything else needed to call it correctly — states, debtor scope, limits, legal-use restrictions — is present.

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, but the description adds real meaning: it clarifies which of the schema's four accepted state codes actually work (CO/CT/OR) and explains the VT error behavior the schema only gestures at. Parameter-level syntax like the debtor_name fragment matching is left to the schema.

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?

States a specific verb and resource ('Search UCC financing-statement filings by debtor business name') plus the exact state scope, so an agent knows precisely what the tool returns. It implicitly separates itself from the sibling ucc_new_filings through the 'by debtor business name' query mode, but never names that sibling or draws the contrast explicitly.

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-not guidance: business debtors only, individuals excluded, and hard FCRA exclusions for credit/employment/insurance/housing decisions. It doesn't name an alternative tool for adjacent needs or state preconditions like credentials, so it stops short of full routing guidance.

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

All Ucc Liens toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources