Skip to main content
Glama

Cobalt Ucc

cobalt_ucc
Read-onlyIdempotent

UCC liens for a business, returns Uniform Commercial Code filings (secured party, filing date, filing number, status) recorded against a company. Covers 11 states. Use to detect existing liens on collateral for lending/underwriting. Example: cobalt_ucc({ searchQuery: "Acme LLC", state: "TX", _apiKey: "your-key" })

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": "TX",
      "_apiKey": "your-cobalt-api-key",
      "searchQuery": "Acme LLC"
    },
    "name": "cobalt_ucc"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesTwo-letter US state code, e.g. "TX", "CA". UCC coverage is limited to 11 states.
_apiKeyYesCobalt Intelligence API key.
searchQueryYesCompany legal name or Secretary-of-State entity id (sosId).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description usefully adds the 11-state coverage limit and enumerates the returned fields, but says nothing about pagination, result caps, or what happens when a state is outside coverage. That is adequate-but-thin against an annotation-covered tool.

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?

Three sentences, front-loaded with what is returned and followed by the use case and a concrete call example. The parenthetical field list is efficient, though the example partially restates the schema's own example block.

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?

There is no output schema, and the description compensates by naming the four returned fields, which is exactly the gap an agent would otherwise hit. Combined with the coverage limit and required-parameter example, it is nearly complete; only edge behavior for unsupported states is unaddressed.

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 all three parameters are already documented in the schema, including the state code format and that searchQuery accepts a legal name or sosId. The description's worked example shows the parameters in use but adds no new semantic detail beyond the schema, making baseline 3 correct.

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?

The description uses a specific verb+resource framing: it returns Uniform Commercial Code filings (secured party, filing date, filing number, status) recorded against a company, and states the 11-state coverage limit. It does not name a sibling tool, so an agent must infer the distinction from cobalt_business_search on its own.

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?

It gives a clear use context — detecting existing liens on collateral for lending/underwriting — which tells the agent when this tool is appropriate. It offers no explicit exclusions or 'use X instead' routing to alternatives, so the guidance stops short of the top band.

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.