Skip to main content
Glama

Gwinnett Index

by net.gwindex

Resolve governing jurisdiction — ALWAYS CALL FIRST

resolve_jurisdiction

ALWAYS CALL THIS FIRST for any Gwinnett County address or parcel. Returns which government actually regulates the land — one of 17 cities, or unincorporated Gwinnett County (67.3% of the county) — with its code citation, a confidence band and the distance to the nearest jurisdiction boundary. A mailing address is NOT the jurisdiction: most "Duluth, GA" addresses are not in the City of Duluth.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pinNoGwinnett parcel PIN, e.g. "7119 100"
band_mNoUncertainty band in metres (default 150)
addressNoStreet address, e.g. "3175 Peachtree Industrial Blvd, Duluth GA"

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the return values (jurisdiction, code citation, confidence band, distance) and the 'always call first' behavior. It doesn't mention potential errors or side-effect safety, but the tone implies a read-only query, and the output details provide substantial transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no wasted words. Front-loaded with the critical 'ALWAYS CALL THIS FIRST' directive, followed by precise output details and a high-value caveat. Every sentence earns its place.

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?

Despite lacking an output schema, the description explains key return fields and the core caveat. It could explicitly state that pin and address are alternative identifiers, but this is implied by 'any Gwinnett County address or parcel'. Overall, quite complete for its complexity.

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%, so the baseline is 3. The description adds meaningful context beyond the schema, particularly the warning that a mailing address does not determine jurisdiction, which directly informs how to interpret the 'address' parameter. It also implicitly ties 'confidence band' to 'band_m'.

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 clearly states the tool's function: resolving governing jurisdiction for Gwinnett County addresses or parcels. It specifies the output (one of 17 cities or unincorporated county, code citation, confidence band, distance to boundary) and distinguishes itself from siblings by declaring 'ALWAYS CALL FIRST' as a prerequisite.

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?

Provides explicit usage guidance: 'ALWAYS CALL THIS FIRST' for any Gwinnett County address or parcel, establishing its role relative to sibling tools. Adds a crucial caveat about mailing addresses not being equivalent to jurisdiction, which helps agents avoid common errors.

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

All Gwinnett Index toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool targets a distinct action: retrieving case details, fetching code sections, listing jurisdictions, resolving a specific address/parcel, and searching cases. There is no functional overlap, and the descriptions clearly separate their purposes.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: get_case, get_code_section, list_jurisdictions, resolve_jurisdiction, search_cases. The naming is uniform and follows standard REST-like conventions.

Tool Count5/5

Five tools is well-scoped for a land-use index server. Each tool covers a core function without redundancy, and the count is neither too sparse nor too heavy for the domain.

Completeness4/5

The tool set covers the essential workflows: finding cases, retrieving case details, looking up code sections, and determining jurisdiction. Minor gaps exist (e.g., no direct tool for parcel geometry or zoning map), but the core functionality is complete.

Resources