Skip to main content
Glama
Sign In

Indiana Code

by org.openindianalaw
OverviewDiscussionsAdmin

Browse Indiana county local rules

local_rules_browse
Read-onlyIdempotent

Posted current local-rule compilations for Indiana counties. No county lists all 92 with posted/missing status. county is a slug such as 'lake-county' or a name such as 'Lake'. Missing counties name Trial Rule 81(G); this tool does not contact clerks. Unofficial; not legal advice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "local_rules_browse"
  }
}

Input Schema

NameRequiredDescriptionDefault
countyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds useful context: it does not contact clerks, missing counties name Trial Rule 81(G), and results are unofficial and not legal advice.

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 description is short and front-loads the core resource scope before explaining the optional county behavior and disclaimers. The sentence 'No county lists all 92 with posted/missing status' is slightly awkward but still efficient.

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 values need not be described. The description covers the browse scope, optional county filter, missing-county behavior, and legal disclaimer; the main omission is an explicit comparison with local_rules_search.

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 carries the burden for the single optional parameter. It explains that county can be a slug like 'lake-county' or a name like 'Lake', and that omitting it lists all counties.

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?

The description identifies the resource as 'posted current local-rule compilations for Indiana counties' and the title supplies the browse action. It does not explicitly distinguish this from the sibling local_rules_search, but the resource scope is clear.

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 explains that omitting the county lists all 92 with posted/missing status, and it describes how missing counties are represented. It does not explicitly say when to use local_rules_search instead, which keeps it below a 5.

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