Skip to main content
Glama

Tn Statute

tn_statute
Read-onlyIdempotent

Get a section of the Tennessee Code Annotated (T.C.A.), Tennessee state law, by citation. "39-13-202" is first degree murder; "66-28-301" is the security-deposit statute. Accepts natural forms: "39-13-202", "T.C.A. 39-13-202", "Tenn. Code Ann. section 39-13-202". Returns the statutory text, catchline, chapter context, and the "Acts ..." legislative history when the text carries one, but NOT case-law digest ("Notes to Decisions"), which this pack excludes. IMPORTANT: this is a POINT-IN-TIME snapshot frozen at 2021-05-21 (release 76 of Public.Resource.Org's scan), not the current code, Tennessee's only current electronic TCA is behind a LexisNexis login/session wall this pack cannot reach (confirmed by Tennessee Court of Appeals litigation; see this pack's README). Every response states current_through explicitly. Also returns later_acts: a dated, linked overlay of every Public Chapter this pack's own home-built index (built from Tennessee General Assembly Effective Reports and bill text, since Tennessee publishes no citation-to-act index) shows touching this exact citation since the 2021-05-21 snapshot (Public Chapter number, General Assembly, bill id, link to the bill text), NOT merged into the text, explicitly labelled so, with sessions_checked naming every Effective Report the index covers even when later_acts is empty. Use for "what does T.C.A. 39-13-202 say" or to check a Tennessee statute AND whether it has been amended since 2021-05-21. All 68 published titles are covered. 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": {
      "citation": "39-13-202"
    },
    "name": "tn_statute"
  }
}

Input Schema

NameRequiredDescriptionDefault
citationYesSection citation, e.g. "39-13-202" (murder) or "66-28-301" (security deposits). Title-chapter-section; the title is the part before the first dash.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Well beyond the annotations, the description discloses the point-in-time freeze at 2021-05-21, that every response states current_through, that later_acts is a separate non-merged overlay with sessions_checked, that the 'Notes to Decisions' material is absent, and that access is keyless. These are exactly the traits (freshness, completeness, auth) an agent cannot infer from readOnly/idempotent hints.

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?

Purpose is front-loaded in the first sentence, followed by examples, accepted formats, return contents, and the snapshot caveat in a sensible order. It runs long and the parenthetical about Tennessee Court of Appeals litigation and the README is supporting justification rather than operational guidance, costing it a point.

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 return-value burden and does so fully: statutory text, catchline, chapter context, 'Acts ...' history, later_acts contents, and current_through. For a single-parameter lookup with clear freshness caveats, nothing material is missing.

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% and the schema already defines the citation format, so the baseline is 3. The description adds real meaning by listing accepted natural forms ('T.C.A. 39-13-202', 'Tenn. Code Ann. section 39-13-202'), which tells the agent normalization is handled rather than requiring exact input.

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 description names a specific verb and resource ('Get a section of the Tennessee Code Annotated ... by citation') and fixes scope with two concrete citation examples plus 'All 68 published titles are covered.' It never names a sibling tool or states the boundary with tn_search, so differentiation is left to the agent.

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?

It gives explicit use cases ('what does T.C.A. 39-13-202 say' and checking whether a statute has been amended since 2021-05-21) and an explicit exclusion (case-law digest 'Notes to Decisions' is not included). No alternative tool is named for the excluded case-law need, which is the one routing gap.

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.