Skip to main content
Glama

Illinois Business Signals

Service health (free)

health
Read-onlyIdempotent

Free. Is the service up, and how fresh is each data source? status is ok, or stale when a source is older than its threshold. Inputs: none. Price: free, no key needed. Example call: {} Example response: {"status":"ok","data_freshness":"2026-11-13","sources":{"ilsos_corp":{"data_as_of":"2026-11-13","age_days":1,"records":0}},"version":"0.1.0"}

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description goes further by defining the status semantics and the meaning of "stale" (a source older than its threshold), and the example response reveals fields like age_days and version that annotations cannot express.

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 opening line front-loads the question and the status semantics, and the input/price/example blocks are easy to scan. Minor waste: "Free." appears both as the first word and again as "Price: free, no key needed," and the empty example call adds little.

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?

This is a trivial no-argument read tool with no output schema, yet the description supplies a full example response so an agent knows the return shape (status, data_freshness, per-source records/age_days, version). Nothing needed to call or interpret it 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?

There are zero parameters, so the baseline is 4. The description explicitly confirms "Inputs: none" and the example call is the empty object, which matches the empty properties schema with no ambiguity.

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 states a specific question the tool answers ("Is the service up, and how fresh is each data source?") plus the exact status vocabulary (ok / stale against a per-source threshold). That makes it unmistakably a liveness/freshness probe, distinct from data-query siblings like coverage, new_filings, or the verify_* tools.

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

Usage Guidelines3/5

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

Usage is implied rather than prescribed: an agent can infer this is a pre-flight check, but the text never says "call before other tools" or when not to bother. No sibling alternative is named, and "Inputs: none" is the only explicit constraint.

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