Skip to main content
Glama

Tx Codes

tx_codes
Read-onlyIdempotent

List the Texas codes with their subjects, Penal Code is PE, Family Code is FA, Tax Code is TX, and so on. Keyless. Use when you know the subject but not the code abbreviation, before calling tx_statute.

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": {},
    "name": "tx_codes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds 'Keyless', which is genuinely useful operational context an agent cannot get from the annotations. It stops short of describing the shape of the returned list, which keeps it from a 5.

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?

Two short sentences, front-loaded with the action and followed by the routing advice. The trailing 'and so on' is slightly loose but does signal that the abbreviation list is illustrative rather than exhaustive, which is worth the words.

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 zero-parameter list tool with rich annotations and no output schema, the description covers what it returns (codes plus subjects), that it needs no key, and how it fits with tx_statute. Only the return format (e.g., whether subjects are searchable strings) is left implicit, a minor gap.

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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter meaning to add. The description correctly implies a no-argument call and does not invent inputs.

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 ('List the Texas codes with their subjects') and immediately grounds it with concrete abbreviation examples (PE, FA, TX), so an agent knows exactly what comes back. It also distinguishes itself from the sibling tx_statute by positioning itself as the lookup step that precedes it.

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 an explicit trigger condition ('when you know the subject but not the code abbreviation') and names the follow-up tool (tx_statute), which is the only plausible alternative here. Nothing about when to reach for this versus tx_statute is left to inference.

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.