Skip to main content
Glama

Cobalt Business Search

cobalt_business_search
Read-onlyIdempotent

Look up a US company's Secretary-of-State registration & status, returns entity name, standing/status, SOS entity id, entity type, filing date, officers, registered agent, and address. Live from the state SOS portal (all 50 states + DC). Example: cobalt_business_search({ searchQuery: "Cobalt Intelligence", state: "UT", _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": "CA",
      "_apiKey": "your-cobalt-api-key",
      "searchQuery": "Apple Inc"
    },
    "name": "cobalt_business_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesTwo-letter US state code, e.g. "CA", "NY", "TX", "DE".
_apiKeyYesCobalt Intelligence API key (20 free lookups at cobaltintelligence.com).
liveDataNoOptional. Force a fresh live pull from the state portal (slower, may return a retryId) instead of allowing recent cached data.
searchQueryYesCompany legal name (e.g. "Apple Inc") or a Secretary-of-State entity id (sosId) to look up.

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 cover the safety profile (readOnly, idempotent, non-destructive), so the description's added value is the data provenance (live state SOS portal, 50 states + DC) and the enumerated return fields, which is important because there is no output schema. It does not mention retryId handling, pagination, or that results may be cached by default, which slightly tensions with the "Live from the state SOS portal" claim.

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 capability and return fields, then a compact example. The example partially duplicates the schema's examples array but earns its place by showing the required _apiKey convention in context.

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?

Without an output schema, listing returned fields compensates well, but a search tool that may return multiple or zero matches says nothing about result cardinality, ambiguity handling, or retryId follow-up. Complete enough to invoke, not complete enough to interpret results confidently.

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%, and every description sentence about inputs (company legal name or SOS entity id, state, api key) merely restates what the schema already documents. Baseline 3 is appropriate when the schema carries the parameter burden.

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 concrete verb and resource ("look up a US company's Secretary-of-State registration & status") and enumerates the returned entity fields plus the jurisdiction scope (all 50 states + DC). This implicitly separates it from TIN verification and UCC siblings, but no sibling is named for explicit differentiation.

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?

Usage is implied by the domain (company registration lookup by name or SOS entity id) and reinforced by a worked example, but there is no explicit when-to-use vs. when-to-use-another-tool guidance and no statement of what this tool does not cover.

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.