Skip to main content
Glama

Illinois Business Signals

What is covered (free)

coverage
Read-onlyIdempotent

Free. Call this first to see what is covered before paying: data sources and how fresh they are, the 102 Illinois counties with record counts, the verdict and county_source meanings, known gaps, prices, and how to authenticate or pay (including this MCP endpoint). Inputs: none. Price: free, no key needed. Example call: {} Example response: {"service":"Illinois Business Signals","endpoints":[...],"sources":[...],"known_gaps":[...],"plans":{...},"mcp":{"path":"/mcp",...}}

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": "coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds meaningful context beyond annotations: it is free, requires no key, reveals prices and authentication/payment paths, and shows an example response shape.

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?

The description is front-loaded with purpose and usage, then concise input/price details and useful examples. It repeats 'Free' and price information, but the repetition is minor and the example response earns its place because no output schema exists.

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?

For a zero-parameter discovery tool without an output schema, the description covers purpose, usage, cost, authentication, payment, and an example response. Nothing essential is missing for an agent deciding whether and how to call it.

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?

The schema has zero parameters, so the baseline is 4. The description reinforces this with 'Inputs: none' and an example call of {}, which removes ambiguity for the agent.

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?

The description uses a specific action ('Call this first to see what is covered') and enumerates the resource contents: data sources, freshness, counties, meanings, gaps, prices, and authentication/payment details. It clearly distinguishes this as a free discovery/coverage tool rather than a data retrieval or verification tool.

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?

It explicitly says to call this first before paying, giving a clear sequencing rule for agents. It does not name or contrast sibling tools, but the 'before paying' context is sufficient for this free discovery endpoint.

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