Skip to main content
Glama

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.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "act": "5",
      "chapter": "720",
      "section": "9-1"
    },
    "name": "il_compiled_statute"
  }
}

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. Changed2 schema fields changed
    • changedInput schema / properties / act / description
      Previous value: -"Act number within the chapter — the part after ILCS and before the slash, e.g. \"5\". Omit if passing `citation`."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 / citation / description
      Previous value: -"The full citation in one string, e.g. \"225 ILCS 155/30\". Alternative to chapter/act/section — either works."New value: +"The full citation in one string, e.g. \"225 ILCS 155/30\". Alternative to chapter/act/section, either works."
  2. 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"
      -]
  3. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds two genuinely useful facts beyond that — "Keyless" (no auth needed) and that the response carries a data_as_of timestamp — but says nothing about behavior on an unresolvable citation or about text size/truncation.

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-loaded with the core action and scope, then examples, then the input-form note, then return value and auth. Every sentence carries information; the citation examples are slightly dense but earn their place by teaching the format.

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?

For a 4-param, all-optional lookup with no output schema, the description covers input formats, return contents (statutory text plus data_as_of), and the keyless auth situation. Only edge behavior on an invalid or ambiguous citation is unaddressed.

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

Parameters3/5

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

Schema description coverage is 100% and already documents chapter/act/section/citation with the same example citations, so the description adds only the framing that the two input styles are alternatives. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ... by citation") and anchors it with two concrete citation-to-subject examples (720 ILCS 5/9-1 = first degree murder, 625 ILCS 5/11-501 = DUI). An agent can immediately tell this is a citation-based full-text fetch rather than a keyword search.

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 explicit trigger phrasings ("what does 720 ILCS 5/9-1 say", "check an Illinois statute a case relies on"), which is clear when-to-use guidance. It does not name a when-not condition or point at the sibling il_statute_search for keyword lookups, leaving that routing to inference.

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.