Skip to main content
Glama

Ks Statute

ks_statute
Read-onlyIdempotent

Get the FULL TEXT of a section of the Kansas Statutes Annotated, Kansas state law, by citation. "K.S.A. 21-5402" is first degree murder. Returns the statutory text. Keyless. Use for "what does K.S.A. 21-5402 say" or to check a Kansas statute a case 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": {
      "section": "21-5402"
    },
    "name": "ks_statute"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionYesSection as cited, e.g. "21-5402" (murder 1) or "8-1567" (DUI). The digits after the dash encode article and section.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 safety is covered. The description adds value beyond them by disclosing the auth model ('Keyless') and the return shape ('Returns the statutory text'), which an agent needs to know before deciding to call.

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 verb and resource, and short overall. There is mild redundancy — 'FULL TEXT ... Returns the statutory text' restates itself, and 'Kansas Statutes Annotated, Kansas state law' doubles up — but nothing is unclear.

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?

A single-param lookup tool with no output schema and full annotation coverage; the description supplies the return contract, an example citation, and the auth model. Nothing an agent needs in order to call it correctly is missing.

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 coverage is 100% and the schema itself already supplies examples ('21-5402' murder 1, '8-1567' DUI) and explains that the digits encode article and section. The description's equivalent example adds little beyond that, so the baseline 3 is appropriate — it reinforces but does not extend parameter meaning.

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 Kansas Statutes Annotated ... by citation' — and immediately grounds it with a concrete example ("K.S.A. 21-5402" is first degree murder). No sibling tool in the list overlaps, so the agent can route here unambiguously.

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?

Gives explicit when-to-use triggers: answering "what does K.S.A. 21-5402 say" and verifying a Kansas statute that a case relies on. It does not state when NOT to use it or name an alternative for other jurisdictions, but the domain is narrow enough that the positive guidance is sufficient.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.