Skip to main content
Glama

Ia Code Search

ia_code_search
Read-onlyIdempotent

Search the Iowa Code by TOPIC or keyword rather than citation, e.g. "landlord security deposit", "concealed handgun permit", "operating while intoxicated". Matches against the Iowa Legislature's own official chapter and section CAPTIONS (not full statutory prose, Iowa does not publish a general-index or full-text search of Code section text, verified live) across all 16 titles, then returns the matching sections (or, if none match at the section level, the matching chapters) with their citations. Use ia_code_section afterward for the full text of a result. 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": {
      "limit": 5,
      "query": "concealed weapon permit"
    },
    "name": "ia_code_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 10, max 25.
queryYesTopic or keywords, e.g. "landlord security deposit".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations, it discloses the single most decision-relevant limitation: matching is against captions only, not statutory prose, because no full-text index exists. It also notes the section-to-chapter fallback and that the service is keyless, which removes an auth-planning step.

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 scope and mechanism lead, followed by return behavior and the next-step recommendation, so nothing important is buried. The parenthetical justification for caption-only matching ("not full statutory prose...verified live") is slightly wordy but earns its place by preempting a false expectation of full-text search.

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?

With no output schema, the description still explains what comes back (matching sections with citations, or chapters as a fallback). For a two-parameter, keyless, read-only search tool, nothing an agent needs in order to call it and interpret results 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?

Schema coverage is 100% and already documents limit's default of 10 and max of 25, so the baseline is a 3. The description adds real meaning by specifying that query should be a topic or keywords rather than a citation, which the schema's brief example only hints at.

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 verb and resource ("Search the Iowa Code") and immediately narrows the mechanism to topic/keyword matching against official chapter and section captions across all 16 titles. It distinguishes itself from citation-based lookup and from ia_code_section, so an agent can pick correctly 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 says when to use it (topic or keyword, with three concrete example queries) and when not to ("rather than citation"), and it routes the follow-up step explicitly to ia_code_section for full text. It also discloses the fallback behavior when no section matches.

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.