Skip to main content
Glama

Sd Search

sd_search
Read-onlyIdempotent

Search the South Dakota Codified Laws BY TOPIC or keyword rather than citation, "landlord security deposit", "concealed pistol permit", "homicide". Matches against the Legislature's own official section and chapter CATCHLINES across the whole Code (not full statutory prose, South Dakota does not publish a full-text search of Code section text, verified live), e.g. "landlord" surfaces sections like "Modification of lease--Written notice by landlord" even in a chapter not named for landlords. Returns matching citations and catchlines; call sd_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": {
      "query": "landlord"
    },
    "name": "sd_search"
  }
}

Input Schema

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

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?

Annotations already cover readOnly, idempotent, non-destructive, open-world behavior, so the description's added value is the substantive part: matching is against official section and chapter catchlines only, South Dakota publishes no full-text Code search, and the service is keyless. That catchline-only constraint materially affects how an agent should interpret empty or partial results.

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 key routing and coverage facts are front-loaded and the whole definition is one dense but navigable paragraph. The parenthetical "(not full statutory prose, South Dakota does not publish a full-text search of Code section text, verified live)" is slightly wordy, but it carries real information rather than filler.

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?

There is no output schema, and the description compensates by stating that results are citations plus catchlines and that sd_statute should be called with a citation for the full text. With only two parameters and full schema coverage, nothing an agent needs in order to call this 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%, with both query and limit documented in the schema itself, so the baseline is 3. The description reinforces query semantics with topical phrasings like "landlord security deposit" and "concealed pistol permit", but adds nothing about limit beyond what the schema already states.

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 opens with a specific verb and named resource — search the South Dakota Codified Laws — and immediately constrains the mode to topic/keyword rather than citation. That scope distinction is what separates it from sd_statute, which the definition also names 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states when to use this tool (topic or keyword lookup) and explicitly when not to (citation lookup), routing the agent to sd_statute for full statutory text. It also discloses the coverage limitation that catchlines, not statutory prose, are matched, which tells the agent when results may be thin.

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.