Skip to main content
Glama
Sign In

Kentucky Code

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Ky Statute

ky_statute
Read-onlyIdempotent

Get the FULL TEXT of a section of the Kentucky Revised Statutes (KRS) — Kentucky state law — by citation. "507.020" is murder; "383.580" is the landlord security-deposit statute. Accepts natural forms: "507.020", "KRS 507.020", "§ 507.020". Returns the current statutory text, the catchline, the "Effective:" date, and the legislative "History:" (the Acts that enacted and amended it). Kentucky publishes the CURRENT text only — a prior (pre-amendment) version's text is not available online, only its existence; this tool says so rather than guessing. Keyless. Use for "what does KRS 507.020 say" or to check a Kentucky statute a case or contract relies on.

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": {
      "citation": "507.020"
    },
    "name": "ky_statute"
  }
}

Input Schema

NameRequiredDescriptionDefault
citationYesSection citation, e.g. "507.020" (murder) or "383.580" (security deposits). Chapter and section separated by a dot; some chapters carry a letter suffix (e.g. "507A.020").

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?

Goes well beyond the readOnly/idempotent annotations: it discloses that only current text is published, that prior pre-amendment versions are unavailable, and that the tool will say so rather than guess. Also notes it is keyless and enumerates the returned fields (text, catchline, Effective date, History).

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-loaded with the core action and scope before the examples and caveats. Slightly dense with illustrative citations, but each clause carries a distinct, usable fact.

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 and a single parameter, the description fully compensates: it describes the return contents and the key limitation (no historical text). Nothing an agent needs to call and interpret the result is missing.

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, but the description adds value by listing accepted natural forms ('KRS 507.020', '§ 507.020') and mentioning letter-suffixed chapters like '507A.020'. This reduces input-formatting errors beyond what the schema shows.

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?

States a specific verb and resource — 'Get the FULL TEXT of a section of the Kentucky Revised Statutes' — with concrete citation examples ('507.020' is murder, '383.580' is the security-deposit statute). An agent can distinguish this from the sibling ky_search, which retrieves broadly, without opening the schema.

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?

Explicitly names when to use it: 'what does KRS 507.020 say' or 'to check a Kentucky statute a case or contract relies on.' Clear context, though it never names ky_search as the alternative for situations where the citation is unknown.

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