Skip to main content
Glama

Ia Code Section

ia_code_section
Read-onlyIdempotent

Get the FULL TEXT of a section of the Iowa Code, Iowa state law, by citation. "714.2" is degrees of theft; "321J.2" is operating while intoxicated (OWI). Returns the statute text plus its amendment history (the Acts that enacted/amended it) and cross-references ("Referred to in ..."), each as a separate field. Pass "year" (2000, or 2004 through the current year) to get a historical edition instead of the current one. Keyless. Use for "what does Iowa Code 714.2 say", "Iowa OWI law", or to check an Iowa 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": {
      "section": "714.2"
    },
    "name": "ia_code_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoOptional. An Iowa Code edition year (2000, or 2004-2026) to retrieve a historical version instead of the current one. 2001-2003 were never published online by the Legislature. Omit for the current (2026) edition.
sectionYesSection as cited, e.g. "714.2" or "321J.2". The chapter is the part before the dot and may carry letters, e.g. "714A.1" or "6B.1".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

With no output schema, the description carries the return-shape burden and does it well: statute text plus amendment history and 'Referred to in' cross-references, each as a separate field. It also discloses that the service is keyless and that the year parameter switches to a historical edition, adding auth and behavior context beyond the readOnly/idempotent annotations.

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 purpose is front-loaded in the first clause and each following sentence adds a distinct fact (examples, return fields, historical editions, keyless access, use cases). It is dense but not padded; the illustrative citation strings are the only mildly expendable text.

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 two-parameter read tool with no output schema, the definition covers what is retrieved, what the response contains, how to request a historical edition, and that no key is needed. Nothing an agent needs in order to call it correctly appears to be 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%, so the structured fields already carry the mechanics; the description still adds meaning by attaching real-world content to sample citations ('714.2 is degrees of theft', '321J.2 is OWI'), which helps an agent confirm it has the right section. The year rule is restated from the schema rather than extended, keeping it below a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 Iowa Code ... by citation') and pins the retrieval mode to a citation rather than a query, which implicitly separates it from a search tool. It never names ia_code_search explicitly, so the sibling differentiation is inferred rather than stated.

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 concrete use triggers ('what does Iowa Code 714.2 say', 'Iowa OWI law', checking a statute a case relies on), which is clear guidance on when to reach for it. There are no exclusions or named alternatives for the case where the user has a topic rather than a citation.

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.