Skip to main content
Glama

Tn Search

tn_search
Read-onlyIdempotent

Search the Tennessee Code Annotated (T.C.A.) BY TOPIC or keyword rather than citation"security deposit", "concealed carry", "DUI per se limit", "homicide". This matches OFFICIAL CATCHLINES/HEADINGS (e.g. "39-13-202. First degree murder." matches "murder"), not the full statutory body text, a word that appears only inside a section's text and not its heading will not be found this way. Returns matching citations, catchlines and chapter context; call tn_statute with a citation for the full text. Same 2021-05-21 point-in-time snapshot as tn_statute. 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": {
      "query": "murder"
    },
    "name": "tn_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 10, max 50.
queryYesTopic or keywords, e.g. "security deposit".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description still adds real behavior: it matches catchlines/headings only, returns citations plus catchlines and chapter context, and uses a fixed 2021-05-21 snapshot. That is useful but a bit terse and says nothing about result ordering or what happens when a query returns no catchline hits.

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?

The key distinction from tn_statute is front-loaded and every sentence carries information an agent needs. It is written as one long multi-clause sentence with the catchline caveat stated twice in slightly different form, which costs some readability.

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?

For a two-parameter, read-only, no-output-schema search tool, the definition covers purpose, matching semantics, return contents, the follow-up call (tn_statute), the data vintage, and the lack of auth. Nothing an agent needs in order to call it correctly is missing.

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 coverage is 100% and already documents both query and limit (default 10, max 50). The description adds useful meaning about what 'query' actually matches against (official catchlines rather than full statutory text) but says nothing further about limit or result shaping, so it stays near the baseline.

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?

The description names a specific verb and resource ('Search the Tennessee Code Annotated') and immediately states the scope that separates it from citation lookup: 'BY TOPIC or keyword rather than citation'. It even contrasts itself with the sibling tn_statute, so an agent can route without inspecting either schema.

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?

It gives explicit when-to-use guidance with concrete example queries ('security deposit', 'concealed carry', 'DUI per se limit'), an explicit when-not-to-use rule (words appearing only in body text will not be found), and a named alternative ('call tn_statute with a citation for the full text').

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.