Skip to main content
Glama

Ia Code Titles

ia_code_titles
Read-onlyIdempotent

List the 16 titles of the Iowa Code with their official names and chapter-number ranges, e.g. Title XVI is Criminal Law and Procedure (chapters 687-916). Routing help for when you know the subject but not the chapter/section number, call this or ia_code_search before guessing a citation. 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": {},
    "name": "ia_code_titles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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 new facts beyond them: the tool is keyless (no authentication) and the payload can be used to validate/rout citations. The annotation_contradiction flag is false. However, the description does not disclose response shape, pagination, or the 'before guessing a citation' behavior as a constraint beyond a suggestion, so it adds moderate rather than rich context.

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 sentences, front-loaded with what the tool returns, followed by routing guidance and the keyless note. The concrete Title XVI example earns its place by making the output format concrete. No filler or restatement of the tool name.

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 zero-parameter, read-only listing tool with no output schema, the description supplies everything needed to call it correctly: what it returns, the granularity (16 titles with chapter ranges), an example entry, and when to use it. No auth or ordering surprises remain.

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?

The input schema takes zero parameters, so there is nothing for the description to disambiguate; this meets the baseline of 4. The description correctly signals that no arguments are needed by presenting the tool as a direct enumeration.

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 uses a specific verb and resource ('List the 16 titles of the Iowa Code') and states exactly what each entry contains: official names and chapter-number ranges, with a concrete example (Title XVI = Criminal Law and Procedure, chapters 687-916). This is clearly distinguishable from ia_code_search and ia_code_section, which operate on chapters/sections rather than the title-level index.

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?

It gives an explicit routing rule: when you know the subject but not the chapter/section number, call this or ia_code_search before guessing a citation. It names the alternative and the precondition, but leaves the choice between the two tools hedged ('this or ia_code_search') rather than specifying which situation selects which, and gives no explicit when-not-to-use case such as already holding a section number.

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.