Skip to main content
Glama
Sign In

Indiana Code

by io.github.pipeworx-io
OverviewDiscussionsAdmin

In Code Search

in_code_search
Read-onlyIdempotent

Search the Indiana Code BY TOPIC or keyword rather than citation — "traffic oversized vehicle permit", "landlord retaliatory eviction", "concealed handgun license". Returns ranked sections with their citations across all 37 Indiana Code titles; use in_code_section afterward for the full text of one. 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": {
      "limit": 5,
      "query": "landlord retaliatory eviction"
    },
    "name": "in_code_search"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety burden is lifted. The description adds real context the annotations cannot: ranked result ordering, citations returned per section, coverage across all 37 titles, and 'Keyless' (no auth required). It does not discuss pagination limits, but limit defaults are in the schema.

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?

Front-loads purpose and usage with illustrative examples, then covers return shape and hand-off. Efficient overall, though the three inline example queries add bulk that the schema example already partly supplies.

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 carries return-value burden and does so ('ranked sections with their citations'). Combined with annotations covering the safety profile and a fully documented 2-param schema, an agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters are already documented (query examples, limit default 10 / max 25). The description adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

Specific verb (search) plus resource (Indiana Code) and an explicit contrast with the wrong approach ('BY TOPIC or keyword rather than citation'). It also names the sibling it hands off to (in_code_section), letting an agent distinguish it from the rest of the tool set 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?

States the triggering condition (topic/keyword questions), the anti-pattern it replaces (citation lookup), and the follow-up tool for full text. Concrete example queries illustrate the expected input register, so routing is unambiguous.

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

All Indiana Code toolsInspect
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.

Resources