Skip to main content
Glama
Sign In

Untax

by io.untax
OverviewDiscussionsAdmin

gisdb_search_catalog

Idempotent

Search county CAD and property-record export availability across Tennessee and Georgia. Unavailable packages report unknown counts and prices; output coordinate systems remain unknown until verified.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "state": "<state>"
    },
    "name": "gisdb_search_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional county name search filter (e.g. 'Hamilton', 'Knox', 'Fulton')
stateYesTwo-letter state abbreviation (e.g. 'TN', 'GA')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare openWorldHint=false, idempotentHint=true and destructiveHint=false, but the description adds meaningful caveats the agent could not get elsewhere: unavailable packages return unknown counts and prices, and coordinate systems stay unknown until verified. That is real data-quality context that affects how results must be interpreted; only the odd readOnlyHint=false on a 'search' tool goes unexplained.

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 tightly written sentences with no filler, and the scope statement leads. The phrasing is densely compressed ('property-record export availability', 'output coordinate systems remain unknown until verified'), which costs a little immediate clarity, 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 no output schema, the description does carry some of the return-value burden by describing what results report (counts, prices, coordinate systems) and how missing data appears. For a 2-parameter, single-state-scoped catalog lookup that is close to sufficient; only the shape of the result list itself is left unstated.

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%, so both parameters (query, state) are already fully documented with examples and constraints. The description adds nothing about parameter behavior — not whether query is a substring match, case-insensitive, or scope-limited by state — so the baseline 3 applies.

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 ('Search county CAD and property-record export availability') plus an explicit geographic scope (Tennessee and Georgia), which is far more informative than the bare tool name. It does not name or differentiate against nearby siblings such as gisdb_get_metadata, leaving the agent to infer that this one is an availability index rather than a data fetcher.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the description frames the tool as a way to check whether export packages exist, which suggests calling it before download/quote tools, but never says so. There are no stated preconditions, no exclusions, and no alternative named for retrieving actual parcel data.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Untax toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources