Skip to main content
Glama
Sign In

Ucc Liens

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Ucc New Filings

ucc_new_filings
Read-onlyIdempotent

List recent UCC financing-statement filings for a state since a given date — a lender-activity signal (who is extending secured credit to which businesses, and when). Business debtors only. Optionally filter by secured-party (lender) name. Same state coverage and limits as ucc_search. 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": {
      "since": "2026-09-01",
      "state": "CO"
    },
    "name": "ucc_new_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax filings to return (default 20, max 100).
sinceYesISO date (YYYY-MM-DD) — return filings on or after this date.
stateYesTwo-letter state code: CO, CT, OR, or VT (VT always errors — see tool description).
secured_partyNoOptional: filter to filings naming this secured party (lender), substring match.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower, and the description adds genuine context: business-debtor-only scope, the FCRA-use restriction, and parity with ucc_search limits. The schema points to the tool description for "VT always errors," yet the description never mentions that behavior — a notable omission.

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 the purpose and signal, then layers constraints compactly; every sentence carries information. Slightly lengthened by duplicated compliance caveats ("Not a consumer report" plus the FCRA line) that overlap in intent.

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

Completeness3/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 carry more of the return-value burden — it never says what a filing record contains (debtor, secured party, filing date, etc.). It also fails to cover the VT-always-errors behavior that the schema explicitly delegates to the tool description, leaving a gap an agent would hit at call time.

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 description coverage is 100%, so baseline is 3. The description restates the optional secured-party (lender) filter and the state/date scope but adds no syntax, matching behavior, or format detail beyond what the schema already documents.

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 ("List recent UCC financing-statement filings") with the scope (a state, since a given date) and explains the signal it represents (lender activity toward business debtors). It references the sibling ucc_search only for parity of coverage/limits, without saying how the two tools differ in intent, so an agent still has to infer which 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 Guidelines3/5

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

Provides a real when-not in the FCRA exclusion ("Not for use in credit, employment, insurance or housing eligibility decisions") and scopes to business debtors only. However it gives no explicit condition for choosing this over ucc_search beyond "same state coverage and limits," leaving the alternative routing implied rather than stated.

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