Skip to main content
Glama

New US business registrations (NY, CO, CT, OR)

find_new_business_registrations
Read-onlyIdempotent

Newly registered LLCs, corporations and nonprofits from official state open data for NY, CO, CT and OR: name, state, entity type, formation date, status, county, city, ZIP. Use for new-business lead lists. No personal contact data. Max 10 rows per call; window up to 31 days.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_new_business_registrations"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipNoZIP code.
cityNoCity.
daysNoFormed in the last N days (default 7).
limitNoRows to return (default 10).
stateNoAny of NY, CO, CT, OR (default all).
countyNoCounty.
date_toNoWindow end, YYYY-MM-DD.
date_fromNoWindow start, YYYY-MM-DD.
entity_typeNoe.g. LLC, CORPORATION.
name_containsNoBusiness name contains.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description does add genuinely useful operational limits (max 10 rows per call, window up to 31 days) and flags the absence of personal contact data, but on its own it leaves open how to retrieve more than 10 rows (no offset/pagination parameter exists) and how results are ordered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense paragraph with zero filler: data source and entity scope first, then returned fields, then use case, then hard limits. Every clause carries information an agent would otherwise have to guess.

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 10 optional parameters, no output schema and no annotations for return shape, the description usefully enumerates the returned fields and states the row and window caps. The only material omission is what happens past the 10-row ceiling, since no pagination parameter exists and the description does not explain how to page or narrow further.

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 every parameter is already documented in the schema, including bounds and defaults. The description reinforces the state scope and the 31-day window but adds no syntax or format detail beyond what the schema supplies; baseline 3 applies.

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 names a specific resource (newly registered LLCs, corporations and nonprofits), its authoritative sources (official state open data for NY, CO, CT, OR) and the returned fields. It is unambiguous on its own, but it never distinguishes itself from lead-generation siblings such as find_funding_leads, so an agent must infer the split from the resource name alone.

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?

'Use for new-business lead lists' gives a clear positive use case, and 'No personal contact data' sets a boundary on what the tool can answer. There is no explicit when-not-to-use guidance or naming of an alternative tool for adjacent needs, which keeps it short of a 5.

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.

Resources