Skip to main content
Glama

Ut Code Search

ut_code_search
Read-onlyIdempotent

Search the Utah Code BY TOPIC or keyword rather than citation, "concealed weapon permit", "landlord retaliatory eviction", "DUI penalties". Returns ranked sections with their citations; use ut_code_section afterward for the full text of one. Full-text search, so it answers questions no citation lookup can. 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": {
      "limit": 5,
      "query": "concealed weapon permit"
    },
    "name": "ut_code_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default and maximum 10, le.utah.gov's Solr proxy ignores the row count and always returns 10, so a larger value cannot be honoured.
queryYesTopic or keywords, e.g. "concealed weapon permit".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max results, default and maximum 10 — le.utah.gov's Solr proxy ignores the row count and always returns 10, so a larger value cannot be honoured."New value: +"Max results, default and maximum 10, le.utah.gov's Solr proxy ignores the row count and always returns 10, so a larger value cannot be honoured."
  2. First observed

TDQS

A4.4/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 behavior, so the safety profile is covered. The description adds real context beyond that: it returns ranked sections with citations, it is full-text rather than exact-match, and it is keyless (no auth required). It omits the result-cap behavior, though that caveat is already carried by the limit parameter's schema description.

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?

Three short sentences, front-loaded with the core distinction (topic vs citation) before the follow-up tool and the keyless note. The example query strings overlap with the schema's own examples, which is mildly redundant but still helps an agent phrase searches.

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 still tells the agent what comes back (ranked sections with citations) and what to do next for full text. For a two-parameter search tool this is sufficient to call it correctly without further exploration.

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 description coverage is 100%, including the limit parameter's unusually detailed explanation of the upstream 10-result cap, so the schema does the heavy lifting. The description's quoted example queries illustrate the kind of string the query parameter expects but add no syntax or constraint details beyond the schema.

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 concrete verb and resource (search the Utah Code) and immediately bounds the mode of search: BY TOPIC or keyword rather than citation. It also distinguishes itself from the citation-lookup path by naming ut_code_section as the follow-up tool for full text.

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 explicit when-to-use guidance (topic/keyword queries, questions no citation lookup can answer) and an explicit next step for the alternative need (use ut_code_section for the full text of a specific section). The two-step workflow is unambiguous.

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.