Skip to main content
Glama

Kolmo Construction

by io.kolmo
OverviewDiscussionsAdmin

Parcel, zoning & overlay lookup

lookup_parcel_by_address
Read-onlyIdempotent

Address-first parcel lookup powering the /permits experience. Geocodes a Seattle-area address (King, Pierce, or Snohomish County, WA), resolves the parcel from the county GIS, and returns zoning, setbacks, overlays (shoreline / ECA / flood / historic), lot area, jurisdiction routing, and prior-permit history. Zoning, setbacks and building facts carry the city/county source they came from (geocode, lot geometry and assessor records do not). Use for "what can be built at 123 Main St Seattle?" or before calling check_permit_requirements / estimate_permit_fee for a specific parcel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesFull street address (e.g., "1234 NE 65th St, Seattle, WA 98115"). Must be in King, Pierce, or Snohomish County, WA.
forceRefreshNoSkip the 30-day cache and re-fetch from county GIS + overlay sources. Default false.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYesSet when the county records the address on this parcel as a second address (e.g. a new house on the lot) and the assessor lists the parcel under parcel.address. Not a snap: the parcel is correct.
foundYes
parcelNo
warningYesSet when the address snapped to a nearby parcel. Confirm with the user before relying on the result.
nextStepsYes
disclaimerYes
attributionYes
addressResolutionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / note
      Added value: +{
+  "description": "Set when the county records the address on this parcel as a second address (e.g. a new house on the lot) and the assessor lists the parcel under parcel.address. Not a snap: the parcel is correct.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • changedOutput schema / required
      Previous value: -[
-  "found",
-  "warning",
-  "nextSteps",
-  "disclaimer",
-  "attribution"
-]New value: +[
+  "found",
+  "warning",
+  "note",
+  "nextSteps",
+  "disclaimer",
+  "attribution"
+]
  2. Changed6 schema fields changed
    • removedOutput schema / properties / attribution / properties / contractorLicense
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / attribution / properties / note
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / attribution / properties / organization
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / attribution / properties / retrievedFrom
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / attribution / properties / url
      Removed value: -{
-  "type": "string"
-}
    • changedOutput schema / properties / attribution / required
      Previous value: -[
-  "organization",
-  "contractorLicense",
-  "url",
-  "sourceUrl",
-  "citeAs",
-  "retrievedFrom",
-  "note"
-]New value: +[
+  "sourceUrl",
+  "citeAs"
+]
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "addressResolution": {},
+    "attribution": {
+      "additionalProperties": true,
+      "properties": {
+        "citeAs": {
+          "description": "Ready-made citation line. Use verbatim.",
+          "type": "string"
+        },
+        "contractorLicense": {
+          "type": "string"
+        },
+        "note": {
+          "type": "string"
+        },
+        "organization": {
+          "type": "string"
+        },
+        "primarySource": {
+          "description": "Present when Kolmo verified but does not author the fact — cite both.",
+          "type": "string"
+        },
+        "retrievedFrom": {
+          "type": "string"
+        },
+        "sourceUrl": {
+          "description": "The specific page these facts render on. Link this, not the site root.",
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "organization",
+        "contractorLicense",
+        "url",
+        "sourceUrl",
+        "citeAs",
+        "retrievedFrom",
+        "note"
+      ],
+      "type": "object"
+    },
+    "disclaimer": {
+      "type": "string"
+    },
+    "found": {
+      "const": true,
+      "type": "boolean"
+    },
+    "nextSteps": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "parcel": {},
+    "warning": {
+      "description": "Set when the address snapped to a nearby parcel. Confirm with the user before relying on the result.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "found",
+    "warning",
+    "nextSteps",
+    "disclaimer",
+    "attribution"
+  ],
+  "type": "object"
+}
  4. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark it read-only, idempotent, and non-destructive. The description adds meaningful behavioral context: it geocodes before resolving the parcel, includes a 30-day cache with a forceRefresh option, and notes which returned fields carry source attribution versus which do not. This goes well beyond the annotations.

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?

The description is dense but each sentence earns its place: purpose, return contents, source-attribution nuance, and explicit use guidance. It is front-loaded with the primary purpose and keeps the alternative routing at the end.

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?

Given the rich output schema, comprehensive input schema, and safety annotations, the description covers all needed context: geographic scope, cache behavior, return categories, source provenance, and when to use it relative to sibling tools. Nothing essential is missing.

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 coverage is 100%, so both parameters are fully documented in the input schema. The description reinforces the address geocoding scope and geographic counties but adds no new parameter meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 states a specific verb and resource: 'lookup_parcel_by_address' geocodes an address, resolves the parcel, and returns zoning, setbacks, overlays, lot area, jurisdiction, and permit history. It distinguishes itself from siblings by explicitly positioning it as the address-first lookup that precedes check_permit_requirements and estimate_permit_fee.

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?

The description explicitly says when to use it: for 'what can be built at 123 Main St Seattle?' and 'before calling check_permit_requirements / estimate_permit_fee for a specific parcel.' It also scopes it geographically to King, Pierce, or Snohomish County, which helps an agent decide whether this tool applies.

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

All Kolmo Construction 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