Skip to main content
Glama

Illinois Code

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Il Compiled Statute

il_compiled_statute
Read-onlyIdempotent

Get the FULL TEXT of a section of the Illinois Compiled Statutes — Illinois state law — by citation. "720 ILCS 5/9-1" is first degree murder; "625 ILCS 5/11-501" is DUI. Pass the full citation as citation ("225 ILCS 155/30") or split it into chapter/act/section. Returns the statutory text with a data_as_of timestamp. Keyless. Use for "what does 720 ILCS 5/9-1 say" or to check an Illinois statute a case relies on.

Input Schema

NameRequiredDescriptionDefault
actNoAct number within the chapter — the part after ILCS and before the slash, e.g. "5". Omit if passing `citation`.
chapterNoILCS chapter, e.g. "720" (criminal offenses), "625" (vehicles), "750" (families). Omit if passing `citation`.
sectionNoSection as cited, e.g. "9-1" or "11-501". Omit if passing `citation`.
citationNoThe full citation in one string, e.g. "225 ILCS 155/30". Alternative to chapter/act/section — either works.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "act": "5",
-    "chapter": "720",
-    "section": "9-1"
-  },
-  {
-    "act": "5",
-    "chapter": "625",
-    "section": "11-501"
-  }
-]New value: +[
+  {
+    "act": "5",
+    "chapter": "720",
+    "section": "9-1"
+  },
+  {
+    "act": "5",
+    "chapter": "625",
+    "section": "11-501"
+  },
+  {
+    "citation": "225 ILCS 155/30"
+  }
+]
    • changedInput schema / properties / act / description
      Previous value: -"Act number within the chapter — the part after ILCS and before the slash, e.g. \"5\"."New value: +"Act number within the chapter — the part after ILCS and before the slash, e.g. \"5\". Omit if passing `citation`."
    • changedInput schema / properties / chapter / description
      Previous value: -"ILCS chapter, e.g. \"720\" (criminal offenses), \"625\" (vehicles), \"750\" (families)."New value: +"ILCS chapter, e.g. \"720\" (criminal offenses), \"625\" (vehicles), \"750\" (families). Omit if passing `citation`."
    • addedInput schema / properties / citation
      Added value: +{
+  "description": "The full citation in one string, e.g. \"225 ILCS 155/30\". Alternative to chapter/act/section — either works.",
+  "type": "string"
+}
    • changedInput schema / properties / section / description
      Previous value: -"Section as cited, e.g. \"9-1\" or \"11-501\"."New value: +"Section as cited, e.g. \"9-1\" or \"11-501\". Omit if passing `citation`."
    • removedInput schema / required
      Removed value: -[
-  "chapter",
-  "act",
-  "section"
-]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), yet the description adds genuinely new facts: what comes back (statutory text plus a data_as_of timestamp) and that it is keyless. Missing anything on error behavior for bad citations, but that is a minor gap.

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?

Four sentences, each load-bearing: purpose, examples, input modes, return shape, usage triggers. Front-loaded with the core capability and no filler.

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?

No output schema exists, and the description compensates by naming the return payload (statutory text + data_as_of). Also covers auth (keyless) and input modes, so an agent has everything needed to call it correctly.

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%, so baseline is 3, but the description adds value by giving real citation strings and clarifying that `citation` is an interchangeable single-string alternative to `chapter`/`act`/`section`. The 'Omit if passing citation' constraints in the schema reinforce this.

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?

States a specific verb and resource — 'Get the FULL TEXT of a section of the Illinois Compiled Statutes' — and anchors it with two concrete citation examples. The full-text-by-citation framing implicitly distinguishes it from the sibling il_statute_search (search vs. exact retrieval), so an agent can pick correctly.

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?

Provides clear usage contexts ('what does 720 ILCS 5/9-1 say', checking a statute a case relies on) and explains the two calling modes (single citation vs. chapter/act/section). It never explicitly names il_statute_search as the alternative for keyword discovery, so there is no stated when-not-to-use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Illinois Code toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources