Skip to main content
Glama

Illinois Business Signals

New Illinois business filings by county

new_filings
Read-onlyIdempotent

Which businesses newly registered in one Illinois county? Newest first, from the Secretary of State files (plus Will County assumed-name filings). Inputs: county (required, one county per call, e.g. Will or DuPage), optional industry (text matched against industry_guess), optional since (YYYY-MM-DD, at most 90 days back, default 30), optional limit (1 to 50, default 20), optional include_foreign (true or false, default true). Price: $0.05 per call, paid per call with x402. A monthly API key also works (one unit per call). Call coverage first (free). county_source says where county came from: office, registered_agent or county_filing. registered_agent means the county is the registered agent's county, so it is approximate (this applies to every corporation). Caveats: industry_guess is a guess from the business name, with industry_guess_basis saying how; it is often null. Foreign companies (formed in another state, registered in Illinois) are included by default and labelled foreign: true; send include_foreign false to leave them out. Every record cites source_url and pulled_at. Example call: {"county":"Will","since":"2026-11-01","limit":5} Example response: {"count":1,"total_matching":1,"records":[{"name":"Maple Street Bakery LLC","entity_type":"LLC","foreign":false,"filing_date":"2026-11-10","county":"Will","county_source":"office","industry_guess":null,"source_url":"https://...","pulled_at":"..."}],"data_as_of":{...},"notes":[]}

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "county": "<county>"
    },
    "name": "new_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoOptional, 1 to 50. Default 20.
sinceNoOptional start date YYYY-MM-DD, at most 90 days back. Default 30 days.
countyYesIllinois county name, for example Will or DuPage. One county per call.
industryNoOptional text matched against industry_guess, for example construction.
include_foreignNoOptional. false leaves out out-of-state companies registered in Illinois. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, closed-world behavior, and the description goes far beyond them: per-call pricing ($0.05 via x402 or API key), a 90-day lookback cap, the meaning of county_source (registered_agent means the county is approximate), and the caveat that industry_guess is a name-derived guess that is often null. This is exactly the behavioral context annotations cannot carry.

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?

Front-loaded with the scoping question, then organized into Inputs, Price, county_source semantics, Caveats, and a worked request/response pair. Every section carries information an agent needs, and the example call is compact and directly reusable.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, but the description supplies an example response with field-level meaning (count, total_matching, data_as_of, notes, source_url/pulled_at citations) plus caveats on nullable fields. Nothing material needed to call or interpret results is missing.

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 already 100%, so the restated inputs default to a baseline, but the description adds genuine meaning: industry is matched against industry_guess (not a controlled taxonomy), registered_agent counties are approximate, and foreign is a label for out-of-state formations registered in Illinois. That is more than the schema conveys on its own.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific question that names the verb (newly registered), the resource (businesses), and the scope (one Illinois county, newest first, Secretary of State plus Will County assumed-name filings). An agent can tell immediately what this returns and how it differs from sibling tools like verify_business.

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 real usage direction: one county per call, call the free coverage tool first, and use include_foreign=false to exclude out-of-state companies. It lacks an explicit statement of when this tool is the wrong choice versus alternatives such as verify_business, so it falls short of full when/when-not guidance.

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