Skip to main content
Glama

Check one parcel

check_parcel
Read-onlyIdempotent

One parcel's stored record and its checks: the county value, last sale, years held, lot, zoning line, water, outbuildings, the recorded signs an owner may sell, and (Colorado) every stored check such as tax delinquency, estate records, code cases, permits, wildfire and flood. Find it by shinnslist key, by street address (with ZIP when you have it), or by latitude and longitude.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_parcel"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoThe shinnslist parcel key, like CO|Boulder|R0012345, from an earlier answer.
latNoLatitude in decimal degrees, with lng.
lngNoLongitude in decimal degrees, with lat.
zipNoThe five-digit ZIP, with address.
addressNoA street address, like Cold Spring Rd. (800 block)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / address / description
      Previous value: -"A street address, like 874 Cold Spring Rd."New value: +"A street address, like Cold Spring Rd. (800 block)"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine value by disclosing the breadth of returned content and the Colorado-specific depth ('every stored check such as tax delinquency, estate records, code cases, permits, wildfire and flood'), but says nothing about failure behavior, ambiguity, or cost/latency.

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

Conciseness3/5

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

Front-loaded with the payload rather than the action, and the middle is a single sprawling clause listing ten-plus data fields. Much of that list is informative for an agent that cannot see an output schema, but it reads as an inventory rather than a structured summary.

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 carries the burden of explaining returns and does so thoroughly, including jurisdiction-specific variation. It falls short only on what happens when a parcel is not found or an address is ambiguous across multiple parcels.

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 all five parameters are documented in the schema itself (key format, lat/lng pairing, ZIP-with-address). The description's only addition is the 'with ZIP when you have it' soft-preference hint and the implication that the three lookup modes are alternatives; it does not state whether key wins if multiple are supplied.

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 the resource ('One parcel's stored record and its checks') and enumerates what is included: county value, last sale, years held, lot, zoning, water, outbuildings, sellable signs, and Colorado-specific checks. An agent can distinguish it from find_parcels (plural search) and run_signal (single check) without opening a schema, though no sibling is named explicitly.

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?

Explains the three lookup modes (shinnslist key, street address with ZIP, or lat/lng), which is real usage context. It never says when to call this instead of find_parcels or explain_grading, nor whether the key from a prior answer is preferred over address re-lookup.

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.

Resources