Skip to main content
Glama
Sign In

Kentucky Code

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Ky Search

ky_search
Read-onlyIdempotent

Search the Kentucky Revised Statutes BY TOPIC or keyword rather than citation — "security deposit", "concealed carry", "DUI per se limit", "homicide". Real full-text search over the statutory body text, not just catchlines: a query like "landlord" surfaces KRS 383.580 ("Security deposits") even though that catchline contains neither word. Returns matching citations and catchlines; call ky_statute with a citation for the full text. 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"
    },
    "name": "ky_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return, default 10, max 50.
queryYesTopic or keywords, e.g. "security deposit return".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive behavior, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: search covers statutory body text, not just catchlines, and returns matching citations and catchlines, with ky_statute as the path to full text.

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?

The description is front-loaded with the core search behavior and then adds only high-value details: full-text scope, return fields, and the ky_statute handoff. The examples and explanation earn their place by clarifying search behavior that might otherwise be misread as catchline-only lookup.

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 keyless search tool with a simple two-parameter schema, the description covers purpose, query style, result shape, and next-step tooling. Although there is no output schema, it sufficiently states that the result contains citations and catchlines.

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 100%, so the schema already documents both parameters, including the limit default and maximum. The description still adds useful query semantics by clarifying that the query is topical/keyword-based rather than a citation and by illustrating full-text behavior that the schema alone does not convey.

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 the Kentucky Revised Statutes by topic or keyword. It explicitly distinguishes this from citation lookup by naming ky_statute as the follow-up tool for full statutory text, so an agent can separate the two tools without opening their schemas.

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?

It gives explicit when-to-use guidance: topic or keyword searches such as "security deposit" or "DUI per se limit" rather than citation lookup. It also names the alternative for full text retrieval (ky_statute with a citation), making the routing decision clear.

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

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