Skip to main content
Glama

Illinois Business Signals

Verify up to 100 Illinois businesses

verify_batch
Read-onlyIdempotent

The same status check as verify_business for 1 to 100 Illinois businesses in one call. Use it for lead lists. A bad item returns an error object in its own slot and is not counted; a batch with no valid item is refused and costs nothing. Inputs: businesses, an array of {name, state, optional city, optional zip}, same limits as verify_business. Price: $1.00 flat per call with x402. Under 50 names, single verify_business calls are cheaper. A monthly API key also works: one unit per valid business. Call coverage first (free). Verdicts:

  • active: Registered and in good standing, or still active with a status flag listed in flags.

  • inactive: The state record shows the entity dissolved, revoked, withdrawn, merged or otherwise no longer active.

  • possible_match: A record with a similar, not identical, name exists. Its status is in match.record_verdict. Confirm with the business's ZIP code, or by comparing the returned name, before relying on it. A similar-name match to a corporation always stays possible_match, because the state publishes no address for corporations.

  • not_found: No matching record in the covered Illinois data. not_found does not mean the business is fake.

  • unknown: A record exists but the data cannot say whether it still operates (Will County DBA filings, or an unrecognised status). 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). possible_match is confirmed only by a matching ZIP, never by city alone. not_found does not mean the business is fake: insurers, banks and other entities chartered outside the Secretary of State, and sole proprietors and general partnerships outside Will County, are not covered. Every record cites source_url and pulled_at. Example call: {"businesses":[{"name":"Maple Street Bakery LLC","state":"IL","zip":"60435"},{"name":"Sample Hardware Co","state":"IL"}]} Example response: {"results":[{"verdict":"active","match":{"name":"Maple Street Bakery LLC","county_source":"office","source_url":"https://...","pulled_at":"..."}},{"verdict":"not_found","match":null}]}

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": {
      "businesses": "<businesses>"
    },
    "name": "verify_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
businessesYes1 to 100 objects of {name, state, city?, zip?}, the same fields as verify_business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, but the description adds real behavior: a bad item returns an error object in its own slot and is not counted, a batch with no valid item is refused and costs nothing, and rejected items are not billed. It stops short of stating rate limits or ordering guarantees of the results array, but the billing and partial-failure semantics are unusually well disclosed.

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?

Well front-loaded and sectioned (Inputs, Price, Verdicts, notes, examples), so an agent can scan it quickly. It is longer than needed because key facts are stated twice — 'not_found does not mean the business is fake' and the ZIP-only confirmation rule each appear in both the verdict list and the trailing notes.

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?

With no output schema, the description correctly takes on the return-value burden: it defines all five verdicts, explains county_source values and the registered_agent approximation, and shows an example response. Coverage caveats (entities chartered outside the Secretary of State, sole proprietors outside Will County) and source_url/pulled_at provenance round it out.

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 100% with only one parameter, so the schema carries the formal definition. The description still adds value by restating the element shape ({name, state, optional city, optional zip}) and anchoring it to verify_business's field limits, plus a concrete example call showing two differently-shaped items.

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 verb+resource+scope: 'The same status check as verify_business for 1 to 100 Illinois businesses in one call.' It explicitly names the sibling it mirrors and differs from (verify_business) and states the batch size bounds, so an agent can distinguish the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives a concrete use case ('Use it for lead lists') and explicit routing rules: under 50 names, single verify_business calls are cheaper, and 'Call coverage first (free).' Payment paths (x402 flat $1.00 vs monthly API key at one unit per valid business) let the agent pick a billing mode deliberately.

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