Skip to main content
Glama

Read a statute or rule

get_statute
Read-onlyIdempotent

Fetch the full text of a statute, rule, or code section: the current codification in the edition this corpus holds. Every answer carries currency (edition, current_through, current_through_basis, last_verified, text_last_changed = when our copy last changed, last_amended_year, effective_date, history_note, status, successor, versions_available) and temporal_note. 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. With as_of, a section amended or enacted after that date returns temporal_warning FIRST, with the history note and, where this corpus kept it, the prior text (prior_text_available; most corpora keep none). A repealed or renumbered section returns status_warning with its successor. currency.status is current | sunset (operative until currency.sunset_date; successor names the version that takes over) | future (not yet operative; effective_date is when it starts) | expired | repealed | renumbered, and anything but current leads with status_warning. Where the later version is held (California sections with more than one version), as_of on or after its operative date returns that text in as_of_version. A U.S. Code section can also be omitted (dropped from the Code by the Office of the Law Revision Counsel and no longer printed; not a repeal): it leads with status_warning too, and the history note says why. A CFR section removed from the eCFR is status removed: status_warning REMOVED names the removal's effective date (currency.sunset_date) and the eCFR point-in-time link for the text in force before it. A former U.S. Code appendix section (usc, "50 U.S.C. App. § 462") returns status former_appendix with the current section(s) in former_appendix, not text. currency.competing_texts lists each printed text of a Texas unit two acts amended without reference to each other.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "jurisdiction": "<jurisdiction>",
      "citation": "<citation>"
    },
    "name": "get_statute"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNoOptional operative date, YYYY-MM-DD (offense, contract, accrual or filing date). When the section was amended or enacted after it, the answer leads with temporal_warning (severity amended_after | enacted_after | text_older_than_as_of | unknown_history), the history note and, when this corpus kept it, the prior text (prior_text_available); otherwise as_of_check says no later change is recorded. On or after a held successor version's operative date, as_of_version carries that version's text.
offsetNoCharacter offset for paging long sections
citationYesSection as commonly cited: "83.49", "16-5-1", "174.02". Multi-code states (TX/CA/NY) need the code name too: "Tex. Penal Code 22.01".
max_charsNoMax characters of body text (default 40000)
jurisdictionYesWhich corpus: any two-letter state code (all 50 states + dc), or fl_statute (Fla. Stat.), fl_rule (FL court rules), fac (Florida Administrative Code, "6A-6.03019"), ga (O.C.G.A.), usc, cfr, fedrule, sg (sentencing guidelines). A state's COURT RULES live in the SAME corpus as its statutes — pass the state code and cite the rule as lawyers there do: "TRCP 166a" (tx), "MCR 2.116"/"MRE 403" (mi), "C.R.C.P. 56" (co), "CR 56"/"RAP 2.5" (wa), "Ohio Civ. R. 56" (oh), "Pa.R.C.P. 1035.2" (pa), "R. 4:46-2"/"N.J.R.E. 403" (nj), "Md. Rule 2-501" (md), "I.R.C.P. 56" (id), "Conn. Practice Book § 23-8" (ct), "N.C. R. App. P. 10" (nc), "Cal. R. Ct. 8.204" (ca), "22 NYCRR 1250.1" (ny), "Tenn. R. Civ. P. 56" (tn), "Ga. Sup. Ct. R. 41" (ga). Rules are in-corpus for all 44 of: ak al ar az ca co ct dc de fl ga hi ia id il in ky ma md me mi mn mo ms mt nc nd ne nj nm nv ny oh or pa ri sc tn tx ut va wa wi wv wy. ks la nh ok sd vt keep no separate rules set — theirs are codified AS statutes ("S.D. Codified Laws § 15-6-10(a)", "K.S.A. 60-256"), and so are the Hawaii evidence rules ("Haw. Rev. Stat. § 626-1, Rule 403").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / as_of / description
      Previous value: -"Optional operative date, YYYY-MM-DD (offense, contract, accrual or filing date). When the section was amended or enacted after it, the answer leads with temporal_warning (severity amended_after | enacted_after | text_older_than_as_of | unknown_history), the history note and, when this corpus kept it, the prior text (prior_text_available); otherwise as_of_check says no later change is recorded."New value: +"Optional operative date, YYYY-MM-DD (offense, contract, accrual or filing date). When the section was amended or enacted after it, the answer leads with temporal_warning (severity amended_after | enacted_after | text_older_than_as_of | unknown_history), the history note and, when this corpus kept it, the prior text (prior_text_available); otherwise as_of_check says no later change is recorded. On or after a held successor version's operative date, as_of_version carries that version's text."
  2. Changed1 schema field changed
    • addedInput schema / properties / as_of
      Added value: +{
      +  "description": "Optional operative date, YYYY-MM-DD (offense, contract, accrual or filing date). When the section was amended or enacted after it, the answer leads with temporal_warning (severity amended_after | enacted_after | text_older_than_as_of | unknown_history), the history note and, when this corpus kept it, the prior text (prior_text_available); otherwise as_of_check says no later change is recorded.",
      +  "type": "string"
      +}
  3. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations only establish that this is a safe, idempotent read; the description adds substantially beyond that. It discloses the currency payload, the precedence rules for warnings (temporal_warning FIRST, status_warning on repeal/renumber/removal), the specific status vocabulary including non-obvious cases like U.S. Code omission and CFR 'removed,' and the fact that most corpora keep no prior text.

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?

Purpose is front-loaded and the content is dense but on-topic. However it is delivered as one very long run-on paragraph mixing core behavior with edge cases (Texas competing_texts, former U.S. Code appendices), with no structure to help an agent scan it, and some sentences restate schema content.

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, the description carries the entire burden of explaining return shape, and it does so comprehensively—enumerating currency fields, warning types, and alternate return modes like former_appendix and competing_texts. An agent can predict the response envelope without trial calls.

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 description coverage is 100% and the as_of schema text already covers the operative-date mechanics, temporal_warning severities, and as_of_version behavior almost verbatim. The description's parameter-level contribution is therefore mostly redundant; its added value lies in the return-value and status discussion, not in parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening clause states a specific verb and resource ('Fetch the full text of a statute, rule, or code section') and pins the version to 'the current codification in the edition this corpus holds.' It does not, however, distinguish itself from siblings like search_statutes or check_citation, so an agent must infer that this is the retrieval tool for a known citation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

There is real when-to-use guidance, but it is scoped to a parameter rather than tool selection: 'For a crime, a contract, a limitations period or a procedural step, establish the operative date first ... and pass it as as_of.' No sibling is named as an alternative for lookup-by-topic or citation validation, so routing between get_statute and search_statutes is left implicit.

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