Skip to main content
Glama
Sign In

Louisiana Code

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Louisiana Law Search

louisiana_law_search
Read-onlyIdempotent

Full-text search of Louisiana law BY TOPIC or keyword — "vehicular homicide", "security deposit lessor", "concealed handgun permit", "wrongful death damages" — across the Revised Statutes, Civil Code, Code of Civil Procedure, Code of Criminal Procedure, Code of Evidence, Children's Code and the Louisiana Constitution, optionally narrowed to chosen code bodies. Returns relevance-ranked sections with citation, heading, the date each was last modified, the total match count, and the doc_id to pass to louisiana_statute for full text. The engine ANDs every word, so two or three specific words outperform a sentence. Keyless; sourced live from the Louisiana State Legislature.

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": "vehicular homicide"
    },
    "name": "louisiana_law_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return, default 20, max 100 (the source renders the first 100 of a larger set).
queryYesTopic or keywords, e.g. "vehicular homicide". Words are ANDed; "a or b" and "a not b" are understood; ""exact phrase"" in doubled quotes matches in order.
bodiesNoLaw bodies to search: RS (Revised Statutes), CC (Civil Code), CCP, CCRP, CE, CHC (Children's Code), CONST, CA, HRULE, SRULE, JRULE. Default: all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already establish read-only, idempotent, non-destructive, open-world behavior. The description adds meaningful behavioral context beyond that: the search engine ANDs every word, results are relevance-ranked, the source is live and keyless, and returned fields include citation, heading, modification date, total match count, and doc_id.

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 front-loaded and dense with useful routing information, but it is longer than strictly necessary and repeats some query syntax already documented in the schema.

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?

Although there is no output schema, the description explains the return shape well enough for an agent to know what to expect. It covers source, search behavior, scoping, and the handoff to louisiana_statute, leaving no major ambiguity for invocation.

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 baseline is 3. The description still adds useful semantics, especially that two or three specific words outperform a sentence and that bodies can optionally narrow the search, though it does not add much beyond the schema for the limit parameter.

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: full-text search of Louisiana law by topic or keyword. It clearly scopes the law bodies covered and distinguishes this search tool from the sibling louisiana_statute by explaining that doc_id is passed there for full text.

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 clear usage context: search by topic or keyword, optionally narrow by code body, and use short ANDed keyword queries rather than sentences. It also points to louisiana_statute as the follow-up for full text, though it does not explicitly state when not to use this tool.

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

All Louisiana 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