kolmo-mcp-server

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). An overlay with offLotFt was mapped that many feet beside the lot, not on it; screen: true marks a county map read inside a city, or a city map its own code calls only a guide, a reason to ask, not the city's designation. Use for "what can be built at 123 Main St Seattle?" or before calling check_permit_requirements / estimate_permit_fee for a specific parcel.

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": {
      "address": "<address>"
    },
    "name": "lookup_parcel_by_address"
  }
}

Input Schema

Name	Required	Description	Default
`address`	Yes	Full street address (e.g., "1234 NE 65th St, Seattle, WA 98115"). Must be in King, Pierce, or Snohomish County, WA.
`forceRefresh`	No	Skip the 30-day cache and re-fetch from county GIS + overlay sources. Default false.

Output Schema

Name	Required	Description
`note`	Yes	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.
`found`	Yes
`parcel`	No
`warning`	Yes	Set when the address snapped to a nearby parcel. Confirm with the user before relying on the result.
`nextSteps`	Yes
`disclaimer`	Yes
`attribution`	Yes
`addressResolution`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 23, 2026

changedOutput schema / properties / attribution / properties / citeAs / description

Previous value: -"Ready-made citation line. Use verbatim."New value: +"Citation line; use verbatim."

changedOutput schema / properties / attribution / properties / primarySource / description

Previous value: -"Present when Kolmo verified but does not author the fact — cite both."New value: +"Kolmo verified, did not author: cite both."

changedOutput schema / properties / attribution / properties / sourceUrl / description

Previous value: -"The specific page these facts render on. Link this, not the site root."New value: +"The page to link, not the site root."

Changed4 schema fields changedOct 10, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- removedOutput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- removedOutput schema / additionalProperties
```
Removed value: -true
```
- removedOutput schema / properties / attribution / additionalProperties
```
Removed value: -true
```

Changed2 schema fields changedSep 23, 2026

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"
+]

Changed6 schema fields changedSep 3, 2026
- 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"
+]
```

Changed1 schema field changedAug 31, 2026

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"
+}

AddedApr 30, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds real context beyond that: a 30-day cache, geographic scope limited to three WA counties, and provenance rules (which facts carry a source citation and which do not). The offLotFt/screen:true caveats are genuinely useful disambiguation, though they edge into explaining return values that the output schema already covers.

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?

Front-loaded with the verb, resource, and scope, and the closing routing sentence is well placed. The mid-section caveat about offLotFt/screen:true is compressed into a run-on that takes a careful read to parse, which costs a point.

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?

An output schema exists and annotations are rich, so the description needn't cover return shape, and its coverage of scope, provenance, and sequencing is strong. It is silent on failure modes — what happens for an address outside King/Pierce/Snohomish or an unlocatable parcel — which is the one thing an agent would still have to discover by calling.

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% and both parameters are fully documented in the schema itself, including the 3–250 char bound, county constraint, and the cache-bypass behavior. The description adds no parameter-level detail (no address format guidance, no discussion of when forceRefresh is worth the cost), so it matches the baseline for schema-does-the-work tools.

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?

States a specific verb chain (geocode → resolve parcel) and an explicit return set: zoning, setbacks, overlays, lot area, jurisdiction routing, prior-permit history. It also names the downstream siblings it feeds (check_permit_requirements / estimate_permit_fee), so an agent can place it in the workflow without opening the schema.

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

Usage Guidelines4/5

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

Gives a concrete triggering utterance ("what can be built at 123 Main St Seattle?") and a sequencing rule relative to two named siblings. No explicit when-not-to-use case or handling for out-of-area addresses, which keeps it short of a 5.

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

All kolmo-mcp-server tools Inspect

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.