Skip to main content
Glama

Sd Statute

sd_statute
Read-onlyIdempotent

Get the FULL TEXT of a section of the South Dakota Codified Laws, South Dakota state law, by citation. "22-16-4" is murder in the first degree; "43-32-13" covers a landlord's notice of lease modification. Accepts natural forms: "22-16-4", "SDCL 22-16-4", "section 22-16-4". Returns the current statutory text, the official catchline, and, when present, the "Source:" line listing every session law that enacted or amended the section (split out into history). South Dakota publishes the CURRENT text only, no per-year historical archive, so a prior (pre-amendment) version of the text is not available; this tool says so rather than guessing. Keyless. Use for "what does SDCL 22-16-4 say" or to check a South Dakota statute a case or lease 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": "22-16-4"
    },
    "name": "sd_statute"
  }
}

Input Schema

NameRequiredDescriptionDefault
citationYesSection citation, title-chapter-section, e.g. "22-16-4" (murder in the first degree) or "43-32-13" (landlord notice of lease modification). Some sections carry a decimal suffix, e.g. "22-16-20.1".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly/idempotent/destructive=false), and the description adds real value beyond them: what is returned (current text, catchline, Source line split into `history`), that the source publishes current text only so prior versions are unavailable, and that access is keyless. It stops short of noting rate limits or page/output size, but the behavioral disclosure is strong.

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 the key constraint (no historical versions) is stated plainly. It is dense with illustrative citations that partly repeat the schema example, but nothing is wasted or buried.

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?

With no output schema, the description carries the return-value burden and does so (text, catchline, Source/history line). For a single-parameter lookup tool this is close to complete; only edge-case behavior for invalid or non-existent citations is left unstated.

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?

Single parameter with 100% schema description coverage, so baseline is 3. The description restates the citation format with extra accepted variants ('SDCL 22-16-4', 'section 22-16-4'), which is marginally useful but largely duplicates what the schema already documents.

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 South Dakota Codified Laws') plus the lookup key ('by citation'), and backs it with two concrete citations so an agent knows exactly what it retrieves.

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 use cases ('what does SDCL 22-16-4 say', checking a statute a case or lease relies on) and an explicit negative scope (no pre-amendment/historical text). It does not name a sibling alternative for full-text search, so it stops short of full routing guidance.

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.