Indiana Code

Resolve an Indiana Administrative Code citation

iac_resolve_citation

Read-onlyIdempotent

Find IAC citations in free text ('10 IAC 1.5-1-1') and return canonical section ids. year selects a loaded edition; omit it for Current. This is not an Indiana Code (IC) resolver.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "iac_resolve_citation"
  }
}

Input Schema

Name	Required	Description	Default
`text`	Yes
`year`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds non-obvious context beyond that: `year` selects among editions that are *loaded*, implying unavailable years are not serviced. It does not address what happens when text contains no valid citation or multiple citations, which is the remaining behavioral 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?

Three short sentences, zero filler: purpose and output first, parameter behavior second, sibling exclusion last. Every sentence carries distinct information.

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?

An output schema exists, so return-value explanation is unnecessary, and both parameters plus the IC boundary are covered. The one gap is multi-citation / no-match behavior, which matters for a free-text extraction tool whose name ('citations' plural, 'section ids' plural) implies many-to-many resolution.

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 description coverage is 0%, so the description must carry the load, and it does for both params: `text` is free text containing citations (with a format example) and `year` selects a loaded edition with null meaning Current. It does not specify whether multiple citations in one string are all resolved or how non-citation text is handled, keeping it off a 5.

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 (find/resolve) and resource (IAC citations) with an inline example format ('10 IAC 1.5-1-1') and names the output (canonical section ids). It explicitly disclaims being an IC resolver, which distinguishes it from the sibling ic_resolve_citation without the agent needing to open either schema.

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 the operative selection rule for the optional parameter ("omit it for Current") and a clear negative boundary ("This is not an Indiana Code (IC) resolver"), which routes IC text elsewhere. It stops short of naming the exact alternative tool or stating what happens with mixed IAC/IC text, so it is clear context rather than a full when/when-not/alternatives map.

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

All Indiana Code tools Inspect

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.