Skip to main content
Glama
Sign In

Untax

by io.untax
OverviewDiscussionsAdmin

gisdb_get_metadata

Idempotent

Retrieve actual verified technical specifications and export details for a county CAD deliverable, or status unavailable when verified export details are not yet available.

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": {
      "county": "<county>",
      "state": "<state>"
    },
    "name": "gisdb_get_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesTwo-letter state abbreviation (e.g. 'TN', 'GA')
countyYesCounty name (e.g. 'Hamilton')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

The description adds one genuine behavioral fact beyond the annotations: the tool may answer with an 'unavailable' status when verified export details do not yet exist, which prepares the agent for a non-data response. It does not explain the 'verified' qualifier, what is excluded from an unverified result, or why readOnlyHint is false on an apparent read operation.

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?

A single front-loaded sentence with the primary outcome first and the fallback status second; nothing is padding. It is slightly over-adjectivized ('actual verified technical specifications') where plainer wording would read faster.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations covering response shape, the description does at least sketch the two possible outcomes (specs/export details vs. unavailable status). It still leaves the payload opaque — what fields constitute 'export details' — which matters for a tool whose whole job is returning metadata.

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% for both required parameters (state abbreviation, county name), so the schema already carries the semantics. The description mentions county-level scoping but adds no format guidance, examples, or edge-case handling (e.g., how to disambiguate counties with the same name) beyond the schema.

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 ('Retrieve') and a specific resource ('verified technical specifications and export details for a county CAD deliverable'), which is far more informative than a tautology. It does not, however, distinguish itself from any sibling such as gisdb_search_catalog or gisdb_quote_enterprise, so an agent must infer the boundary.

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: an agent can infer it should call this when it needs export metadata for a given county/state pair. There is no explicit when-to-use, no when-not-to-use, and no named alternative for cases where the caller actually wants a delivery or a quote.

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