Skip to main content
Glama

Illinois Business Signals

Verify an Illinois business

verify_business
Read-onlyIdempotent

Is this business registered in Illinois, and is it still active? Illinois only. Inputs: name (2-200 chars), state (IL or Illinois), optional city (max 100), optional zip (5 digits or ZIP+4). Price: $0.02 per call, paid per call with x402. A monthly API key also works (one unit per call). 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: {"name":"Maple Street Bakery LLC","state":"IL","zip":"60435"} Example response: {"verdict":"active","confidence":1,"flags":["annual_report_current"],"match":{"name":"Maple Street Bakery LLC","record_verdict":"active","county":"Will","county_source":"office","source_url":"https://...","pulled_at":"2026-11-14T06:00:00.000Z"},"alternatives":[]}

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": {
      "name": "<name>",
      "state": "<state>"
    },
    "name": "verify_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipNo
cityNo
nameYes
stateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, and the description adds substantial context beyond that: $0.02 per call with x402 payment or a monthly key, provenance of every record (source_url, pulled_at), and the semantics of county_source including the corporation caveat. It stops short of explaining the confidence and alternatives response fields, which appear in the example but are never described.

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-loads the question, then inputs, price, and verdict semantics as scannable bullets with a worked example — dense and well organized. The one waste is the repeated 'not_found does not mean the business is fake', which appears twice almost verbatim.

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?

No output schema exists, so the description must define the return shape, and it does so via enumerated verdicts and a full example response. The remaining gap is that confidence and alternatives are shown but never explained, which matters for an agent deciding how much to trust a possible_match.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage and no enums, the description carries the full burden and does: state accepts 'IL or Illinois' (semantics the schema's bare string cannot express), zip is constrained to 5 or ZIP+4 and is the only field that can confirm a possible_match, and city alone cannot. That is meaning well beyond the schema's length constraints.

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?

Opens with a specific question the tool answers — whether a business is registered in Illinois and still active — plus an explicit scope limit ('Illinois only'). The verb+resource is unambiguous, but the sibling verify_batch (clearly the bulk variant) is never named, so sibling differentiation is only partial.

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 routing guidance ('Call coverage first (free)') and a concrete confirmation workflow for possible_match ('confirm with the business's ZIP code'). It also describes the boundary case (not_found is not fraud, with a list of uncovered entity types), but never says when to use verify_batch instead for multiple lookups.

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