Skip to main content
Glama

Tx Statute

tx_statute
Read-onlyIdempotent

Get the FULL TEXT of a section of the Texas Statutes, Texas state law, by citation. "Texas Penal Code 19.02" is code "PE", section "19.02" (murder). Returns the statutory text and its amendment history. Keyless. Use for "what does Texas Penal Code 19.02 say", "text of Tex. Fam. Code 6.001", or to check a Texas statute a case 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": {
      "code": "PE",
      "section": "19.02"
    },
    "name": "tx_statute"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesTexas code abbreviation, e.g. "PE" (Penal), "FA" (Family), "CP" (Civil Practice and Remedies), "TX" (Tax). Call tx_codes to see them.
sectionYesSection as cited, e.g. "19.02" or "6.001". The chapter is the part before the dot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral facts: 'Keyless' (no authentication needed) and that the response includes both statutory text and amendment history. It stops short of noting failure behavior for invalid code/section pairs.

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 sized to a few tight sentences; the citation example and query phrasings each carry weight. Minor redundancy in 'Texas Statutes, Texas state law' and one extra example clause that could be trimmed.

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 two-parameter lookup with no output schema, the description covers input mapping, authentication ('Keyless'), and the shape of the return value (text plus amendment history). Only edge cases such as invalid citations or non-existent sections are unaddressed.

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, but the description earns above it by translating a natural-language citation into the two-parameter shape and clarifying that the chapter is the portion before the dot. That mapping is real guidance the schema does not supply on its own.

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 Texas Statutes ... by citation') and immediately disambiguates it from tx_codes, which only enumerates abbreviations. The worked example ('Texas Penal Code 19.02' is code 'PE', section '19.02') makes the resource and granularity unmistakable.

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 concrete triggering queries ('what does Texas Penal Code 19.02 say', 'text of Tex. Fam. Code 6.001') and a secondary use case (verifying a statute a case relies on). It also routes code lookup to the sibling tx_codes, though it never states when not to use this tool (e.g., for other states or for case law).

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.