Skip to main content
Glama

Search statutes and rules

search_statutes
Read-onlyIdempotent

Search statutes, COURT RULES and codes by citation or topic, for EVERY U.S. state plus federal. For a specific state, pass state="wi" (any two-letter code, all 50 states + DC) and a topic or section number; add kind="rule" for that state's court rules or kind="statute" for its code. Without state it searches only the kinds named in kinds (default: Florida). Handles citation lookups ("83.49", "174.02") and topic queries ("dog bite strict liability"). Each result carries currency (text_last_changed and, where recorded, last_amended_year / effective_date / status / successor) and corpus_currency gives each corpus's edition and current-through date. OPERATIVE DATE: statute text is the edition this corpus holds, not the law on every date. For a crime, a contract, a limitations period or a procedural step, establish the operative date first (offense, contract, accrual or filing date) and pass it as as_of (YYYY-MM-DD); say so when the text postdates the facts, since an older offense may be charged under a predecessor section. (as_of is taken by get_statute and check_citation.)

Input Schema

NameRequiredDescriptionDefault
qYesCitation or topic query, max 200 chars. With state, "quotation marks" require that exact phrase; other words are ranked, sections holding the most and rarest of them first, and match_mode says whether every row holds every word.
kindNoWith state: scope to one source — "rule" (that state's court rules) or "statute" (its code). Omit to search both; the response's sources field lists what the corpus holds and how many rows of each.
kindsNoUsed only when state is absent. Comma list of corpus kinds: statute (FL statutes), rule (FL court rules), fac (Fla. Admin. Code), ocga, usc, cfr, fedrule, sg, plus any state's own kind ("nc", "tx") and rules kind ("nc-rule", "tx-rule"). Default "statute,rule" is FLORIDA ONLY.
limitNoMax hits (default 5, max 25)
stateNoTwo-letter state code to search that state's corpus (e.g. wi, tx, ny, ca). Covers all 50 states + dc. That corpus holds the state's COURT RULES too in 44 of the 51 — all but ks, la, nh, ok, sd, vt, whose rules of procedure are codified as statutes. Also accepts state="fac" for the Florida ADMINISTRATIVE Code (agency rules such as 6A-6.03019) — state="fl" is the Florida Statutes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / q / description
      Previous value: -"Citation or topic query, max 200 chars"New value: +"Citation or topic query, max 200 chars. With state, \"quotation marks\" require that exact phrase; other words are ranked, sections holding the most and rarest of them first, and match_mode says whether every row holds every word."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description spends its budget on behavior the annotations cannot express: default corpus is Florida, result fields carry currency metadata (text_last_changed, last_amended_year, effective_date, status, successor), and corpus_currency reports edition and current-through dates. The operative-date warning explains a real failure mode (charging an older offense under a predecessor section) that an agent would otherwise miss.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with scope and scoping rules, which is good, but the closing operative-date paragraph spends several sentences instructing the agent to pass as_of, a parameter this tool does not accept, only to disclaim it parenthetically at the end. That block is longer than the tool's own parameter documentation and risks crowding out more relevant guidance.

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?

For a five-parameter search tool with no output schema, the definition covers corpus scope, defaults, result currency fields and the citation-vs-topic distinction well. It is only short of complete because the as_of paragraph belongs to sibling tools and could lead an agent to attempt an unsupported argument on this one.

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; the description still adds meaning, e.g. that state="fac" selects the Florida Administrative Code while state="fl" is the Florida Statutes, and that 44 of 51 state corpora include court rules except ks, la, nh, ok, sd, vt. The as_of discussion does not map to any actual parameter of this tool, which slightly muddies parameter understanding.

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 (search statutes, court rules and codes) plus the scope (every U.S. state plus federal) and the two supported query modes (citation lookup and topic). It is clearly distinguishable from siblings like get_statute and check_citation, which are named as the tools that accept as_of.

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?

Gives explicit routing rules: pass state for one state's corpus, add kind="rule" vs kind="statute" to scope, omit state and use kinds for multi-corpus search with Florida as the default. It also names the alternatives for as_of lookups (get_statute, check_citation), so the agent knows when this tool is the wrong choice.

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.

Resources