Skip to main content
Glama

Il Statute Search

il_statute_search
Read-onlyIdempotent

Search Illinois Compiled Statutes BY TOPIC or keyword rather than citation, "currency exchange license fee", "concealed carry reciprocity", "landlord retaliation". Returns ranked sections with their citations; use il_compiled_statute afterward for the full text of one. Pass chapter + act (e.g. "225" + "155" for 225 ILCS 155) to scope the search to one act's own sections instead of ranking across all ~72,000, use this when you already know which act the answer is in, so a term that is common across many acts still finds the right section. Full-text search, so it answers questions no citation lookup can. Keyless.

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": {
      "query": "currency exchange license fee"
    },
    "name": "il_statute_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
actNoOptional: act number within `chapter` to scope the search, e.g. "155" for 225 ILCS 155. Only that act's sections are searched.
limitNoMax results, default 10, max 25.
queryYesTopic or keywords, e.g. "currency exchange license fee". Can also name an act directly, e.g. "225 ILCS 155 civil penalty".
chapterNoOptional: ILCS chapter to scope the search to one act (pair with `act`), e.g. "225".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / examples
      Previous value: -[
      -  {
      -    "query": "currency exchange license fee"
      -  }
      -]New value: +[
      +  {
      +    "query": "currency exchange license fee"
      +  },
      +  {
      +    "act": "155",
      +    "chapter": "225",
      +    "query": "civil penalty"
      +  }
      +]
    • addedInput schema / properties / act
      Added value: +{
      +  "description": "Optional: act number within `chapter` to scope the search, e.g. \"155\" for 225 ILCS 155. Only that act's sections are searched.",
      +  "type": "string"
      +}
    • addedInput schema / properties / chapter
      Added value: +{
      +  "description": "Optional: ILCS chapter to scope the search to one act (pair with `act`), e.g. \"225\".",
      +  "type": "string"
      +}
    • changedInput schema / properties / query / description
      Previous value: -"Topic or keywords, e.g. \"currency exchange license fee\"."New value: +"Topic or keywords, e.g. \"currency exchange license fee\". Can also name an act directly, e.g. \"225 ILCS 155 civil penalty\"."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the read-only, idempotent, open-world, non-destructive profile, and the description adds genuinely new behavioral facts: results are ranked sections with citations, scoping with act restricts the search to that act's sections only, the corpus is ~72,000 sections, and the tool is keyless (no auth). With no output schema present, the note about ranked sections plus citations is a meaningful disclosure of return 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?

It is front-loaded with the core verb and the example queries that make the tool concrete. The scoping sentence is somewhat run-on, packing the pairing example, the when-to-use condition, and the rationale into one clause, but every sentence still carries information.

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 four-parameter, read-only full-text search with no output schema, the definition covers purpose, result shape (ranked sections with citations), scoping semantics, and authentication expectations. An agent has everything needed to decide between scoped and unscoped searches and to chain into il_compiled_statute.

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 the baseline is 3, but the description adds real meaning beyond the schema: it explains that chapter and act must be paired ("225" + "155" for 225 ILCS 155) and why scoping matters — a term common across many acts still resolves to the right section. That rationale is absent from the parameter descriptions themselves.

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 gives a specific verb and resource ("Search Illinois Compiled Statutes") and immediately distinguishes itself from citation lookup by emphasizing BY TOPIC or keyword, with concrete example queries. It also names the sibling il_compiled_statute for retrieving full text, so an agent can separate the two without opening any schema.

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

Usage Guidelines5/5

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

It states when to use this tool (topic/keyword questions, questions no citation lookup can answer) and when to follow up with il_compiled_statute for full text. It also gives an explicit conditional for the chapter+act scoping path: use it when you already know which act the answer lives in.

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.