kolmo-mcp-server

Permit requirements lookup

check_permit_requirements

Read-onlyIdempotent

Check whether a residential construction project in King/Pierce/Snohomish counties requires a permit. Each result carries verdict — required / exempt / depends / unknown — computed from the jurisdiction's own thresholds, the parcel's overlays (when address is given) and the facts you pass; when it is depends, verdict.questions names the facts to ask the homeowner and pass back. requiresPermit is the rule's default posture, not the answer. Also returns timeline, fee notes, inspection sequence, required submittals, and official source URL — preferring jurisdiction-verified rules. Use for "Do I need a permit to build a deck in Seattle?" or "What permits are required for a kitchen remodel in Bellevue?". Pass address to also receive the structured per-item SubmittalSet (submittals_v2) from the unified permit engine — Seattle is full SDCI fidelity, other 9 verified cities are wa-baseline-stub.

Input Schema

TableJSON Schema

Name	Required	Description
`facts`	No	What the homeowner has said about the scope, keyed by fact. Each result carries `verdict.questions` naming the facts still open; pass them back here. Keys: deckHeightAboveGradeIn, deckAreaSqft, deckAttached, deckOverStoryBelow, deckOnAccessibleRoute, deckServesRequiredExit, roofDeck, deckCovered, deckingBoardsOnly, fenceHeightFt, masonryWallHeightFt, fenceInFrontYard, cosmeticOnly, plumbingMovedOrAdded, newCircuits, gasOrMechanicalWork, structuralOrWallChange, tubOrShowerReplaced, surfacesOpened, windowNewOrEnlargedOpening, windowStructuralChange, windowEgressAffected, windowEnergyDowngrade, sidingStructuralChange, sidingInsulationOrWrbChange, sidingStuccoOrVeneer, roofSheathingReplaced, roofMaterialTypeChange, roofLayersAfter, roofUnitWeightPsf, roofMaterialWeightIncreasePsf, roofFramingChange, roofSkylightsOrMechanical, buildingUnreinforcedMasonry, subfloorOrJoistChange, radiantHeat, plumbingLeakRepairOnly, plumbingLikeForLikeSameLocation, plumbingFixtureInstalledOrReplaced, plumbingFixtureAddedOrMoved, waterHeaterReplaced, plumbingNewOrRelocatedPiping, plumbingConcealedPipeReplaced, electricalLikeInKindMinor, newCircuitsOrPanel, hardwiredFixtureOrAppliance, portableAppliance, hvacMinorPartReplacement, treeDbhIn, treeAlderOrCottonwood, treesRemovedThisYear. Parcel facts (inCriticalArea, inFloodZone, inShoreline, historicOrLandmark) are read from the parcel when `address` is given; pass them only without an address.
`limit`	No	Max matching rules to return (default 25). Narrow with projectType/location before raising it.
`address`	No	Full street address — when provided, the response includes `submittals_v2` from the unified resolver (per-item triggers, source citations, filler actor). Overrides `location` for jurisdiction routing.
`location`	No	City or jurisdiction slug, e.g. "Seattle", "Bellevue", "Tacoma", "king-county-unincorporated"
`projectType`	No	Project type — canonical: kitchen, bathroom, basement, deck, fence, siding, windows, flooring, adu, roofing, hvac, electrical, plumbing, addition
`guardRunLengthFt`	No	Total guard/railing run in the scope of work, feet. A guard is separately permittable from the surface it stands on; a deck exemption does not carry it.
`deckOverStoryBelow`	No	True if any part of the deck is over a basement or a story below. A deck under 30 in is still NOT exempt in Kirkland if it sits over a story.
`deckOnAccessibleRoute`	No	True if the deck is part of an accessible route to a building entrance — an independent permit trigger, separate from height.
`deckHeightAboveGradeIn`	No	Deck walking surface above grade, inches — measured to the grade below at any point within 36 in of the outer edge.

Output Schema

TableJSON Schema

Name	Required	Description
`next`	No
`total`	No
`parcel`	No
`message`	No
`results`	No
`coverage`	No	Present on an unfiltered call: the jurisdictions and project types the catalog covers.
`overlays`	No
`returned`	No
`important`	No
`disclaimer`	No
`trustLevel`	No	"authoritative" or a LEGACY_LLM_SEED warning. Relay the warning if present.
`attribution`	No
`recommendation`	No
`overlayDisclaimer`	No
`authoritativeRulesCount`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 14, 2026

addedInput schema / properties / facts

Added value: +{
+  "additionalProperties": {
+    "type": [
+      "number",
+      "boolean"
+    ]
+  },
+  "description": "What the homeowner has said about the scope, keyed by fact. Each result carries `verdict.questions` naming the facts still open; pass them back here. Keys: deckHeightAboveGradeIn, deckAreaSqft, deckAttached, deckOverStoryBelow, deckOnAccessibleRoute, deckServesRequiredExit, roofDeck, deckCovered, deckingBoardsOnly, fenceHeightFt, masonryWallHeightFt, fenceInFrontYard, cosmeticOnly, plumbingMovedOrAdded, newCircuits, gasOrMechanicalWork, structuralOrWallChange, tubOrShowerReplaced, surfacesOpened, windowNewOrEnlargedOpening, windowStructuralChange, windowEgressAffected, windowEnergyDowngrade, sidingStructuralChange, sidingInsulationOrWrbChange, sidingStuccoOrVeneer, roofSheathingReplaced, roofMaterialTypeChange, roofLayersAfter, roofUnitWeightPsf, roofMaterialWeightIncreasePsf, roofFramingChange, roofSkylightsOrMechanical, buildingUnreinforcedMasonry, subfloorOrJoistChange, radiantHeat, plumbingLeakRepairOnly, plumbingLikeForLikeSameLocation, plumbingFixtureInstalledOrReplaced, plumbingFixtureAddedOrMoved, waterHeaterReplaced, plumbingNewOrRelocatedPiping, plumbingConcealedPipeReplaced, electricalLikeInKindMinor, newCircuitsOrPanel, hardwiredFixtureOrAppliance, portableAppliance, hvacMinorPartReplacement, treeDbhIn, treeAlderOrCottonwood, treesRemovedThisYear. Parcel facts (inCriticalArea, inFloodZone, inShoreline, historicOrLandmark) are read from the parcel when `address` is given; pass them only without an address.",
+  "type": "object"
+}

Changed9 schema fields changedSep 3, 2026

addedInput schema / properties / limit

Added value: +{
+  "description": "Max matching rules to return (default 25). Narrow with projectType/location before raising it.",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}

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

addedOutput schema / properties / coverage

Added value: +{
+  "description": "Present on an unfiltered call: the jurisdictions and project types the catalog covers."
+}

addedOutput schema / properties / returned
```
Added value: +{
+  "type": "number"
+}
```

Changed1 schema field changedAug 31, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "description": "Either a rule set, or a documented coverage gap carrying `important` + `next`. A gap is never evidence that no permit is required.",
+  "properties": {
+    "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"
+    },
+    "authoritativeRulesCount": {
+      "type": "number"
+    },
+    "disclaimer": {
+      "type": "string"
+    },
+    "important": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "next": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "overlayDisclaimer": {
+      "type": "string"
+    },
+    "overlays": {},
+    "parcel": {},
+    "recommendation": {
+      "type": "string"
+    },
+    "results": {},
+    "total": {
+      "type": "number"
+    },
+    "trustLevel": {
+      "description": "\"authoritative\" or a LEGACY_LLM_SEED warning. Relay the warning if present.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed4 schema fields changedAug 8, 2026

addedInput schema / properties / deckHeightAboveGradeIn

Added value: +{
+  "description": "Deck walking surface above grade, inches — measured to the grade below at any point within 36 in of the outer edge.",
+  "type": "number"
+}

addedInput schema / properties / deckOnAccessibleRoute

Added value: +{
+  "description": "True if the deck is part of an accessible route to a building entrance — an independent permit trigger, separate from height.",
+  "type": "boolean"
+}

addedInput schema / properties / deckOverStoryBelow

Added value: +{
+  "description": "True if any part of the deck is over a basement or a story below. A deck under 30 in is still NOT exempt in Kirkland if it sits over a story.",
+  "type": "boolean"
+}

addedInput schema / properties / guardRunLengthFt

Added value: +{
+  "description": "Total guard/railing run in the scope of work, feet. A guard is separately permittable from the surface it stands on; a deck exemption does not carry it.",
+  "type": "number"
+}

Changed1 schema field changedMay 17, 2026

addedInput schema / properties / address

Added value: +{
+  "description": "Full street address — when provided, the response includes `submittals_v2` from the unified resolver (per-item triggers, source citations, filler actor). Overrides `location` for jurisdiction routing.",
+  "type": "string"
+}

Changed2 schema fields changedApr 27, 2026

changedInput schema / properties / location / description

Previous value: -"City or area, e.g. \"Seattle\", \"Bellevue\", \"Kirkland\""New value: +"City or jurisdiction slug, e.g. \"Seattle\", \"Bellevue\", \"Tacoma\", \"king-county-unincorporated\""

changedInput schema / properties / projectType / description

Previous value: -"Type of project, e.g. \"deck\", \"kitchen\", \"addition\", \"fence\", \"ADU\""New value: +"Project type — canonical: kitchen, bathroom, basement, deck, fence, siding, windows, flooring, adu, roofing, hvac, electrical, plumbing, addition"

First observedApr 14, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Even though annotations already declare readOnlyHint=true and destructiveHint=false, the description adds substantial behavioral context. It explains how the verdict is computed (jurisdiction thresholds, parcel overlays, and facts), what happens when verdict is 'depends' (verdict.questions names facts to ask the homeowner), that requiresPermit is the rule's default posture rather than the answer, and that submittals_v2 fidelity differs by city (Seattle full SDCI, others wa-baseline-stub). This goes well beyond the annotations, giving the agent a realistic model of the tool's behavior and edge cases. No contradiction exists.

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 long, but every sentence earns its place. It front-loads the core purpose, then systematically explains the verdict semantics, return fields, usage examples, and the special address behavior. There is no filler or tautology. The structure flows logically from what the tool does, to how to interpret its output, to how to call it effectively. Given the complexity of 9 parameters and a rich output schema, this length is justified and remains concise in intent.

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?

For a tool with 9 parameters, a nested `facts` object, an output schema, and multiple annotations, the description covers the essential workflow: what it does, how to invoke it (including the two natural-language examples), the meaning of key output fields (verdict, requiresPermit), and the special behavior of `address` (submittals_v2 with per-city fidelity). It doesn't repeat parameter-by-parameter details because the schema already provides those, and it doesn't need to describe return structure because the output schema exists. Nothing an agent needs to decide when to call this tool or how to form a correct request is missing.

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% and each parameter already has a detailed description, so baseline is 3. The description adds meaningful usage semantics: it clarifies that passing `address` also returns `submittals_v2` from the unified permit engine, and explains that parcel-related facts in `facts` should only be passed when no address is given ('Parcel facts ... are read from the parcel when `address` is given; pass them only without an address.'). It also orients the `facts` parameter by stating that verdict.questions name the facts to pass back. These enrichments justify a step above baseline.

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 opens with a precise statement: 'Check whether a residential construction project in King/Pierce/Snohomish counties requires a permit.' It names the specific verb, resource, and geographic scope, and immediately distinguishes itself from siblings like answer_permit_question (a Q&A tool) and resolve_permit_submittals (which likely focuses solely on submittals) by framing the core as a permit-requirement check while also returning submittals. This gives an agent a clear, unambiguous purpose.

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?

The description explicitly provides usage examples: "Use for 'Do I need a permit to build a deck in Seattle?' or 'What permits are required for a kitchen remodel in Bellevue?'" This is clear when-to-use guidance. However, it does not explicitly mention when not to use the tool or name alternatives (e.g., get_permit_rule_details for deep-diving a specific rule, or estimate_permit_fee for cost). The context is strong but lacks explicit exclusionary guidance, so it falls 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.