Skip to main content
Glama

Ut Code Section

ut_code_section
Read-onlyIdempotent

Get the FULL TEXT of a section of the Utah Code, Utah state law, by citation, plus its effective date and amendment history. "76-5-203" is murder (Title 76, Utah Criminal Code); "53-5a-102.2" is open/concealed carry. Keyless. Use for "what does Utah Code 76-5-203 say" or to check a Utah statute a case, lease, or citation relies on. Does NOT return superseded/historical full text, only the current version and its amendment citations.

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": {
      "section": "76-5-203"
    },
    "name": "ut_code_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionYesSection as cited, e.g. "76-5-203" or "53-5a-102.2". The title and chapter are the first two dash-separated components; letter-suffixed titles ("75E") and chapters ("5a") are normal.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the description's marginal burden is light — yet it still adds real value: 'Keyless' (no auth needed), the full scope of returned content, and the explicit limitation that only the current version plus amendment citations come back. It doesn't discuss rate limits or response formatting, keeping it short of 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?

The core capability and return payload are front-loaded, followed by usage examples and the historical-text exclusion in a single tight paragraph. There is minor redundancy ('Utah Code, Utah state law') and the inline citation examples make the sentence dense, but nothing is wasted.

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?

With one required parameter, no output schema, and full annotation coverage, the definition covers everything an agent needs: input format, what comes back, availability, and the historical-text boundary. A note on output shape for amendment history would close the remaining 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?

Schema coverage is 100% and the param description already explains dash-separated title/chapter structure, so the baseline is 3. The tool description still adds value by supplying two worked citation examples tied to real sections, giving an agent a mental model of valid formats beyond the schema's abstract rule.

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?

States a specific verb and resource — 'Get the FULL TEXT of a section of the Utah Code' — plus what else is returned (effective date, amendment history) and concrete citation examples ('76-5-203' is murder, '53-5a-102.2' is open carry). It never names the sibling search tool (ut_code_search) to contrast citation-lookup vs. search, so sibling differentiation is functional rather than explicit.

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 clear when-to-use triggers ('what does Utah Code 76-5-203 say', or verifying a statute a case, lease, or citation relies on) and one explicit exclusion (no superseded/historical full text). It stops short of naming the alternative tool an agent should call when it only has a topic rather than a citation.

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.