Kolmo Construction

Permit rule detail

get_permit_rule_details

Read-onlyIdempotent

Enumerate permit rules with full detail — timeline, fee model, inspection sequence, submittals, required contractor specialties. Filter by jurisdiction slug or keyword. Use for "what does a Seattle ADU permit require?" or to list all rules for a jurisdiction. Pass address to also receive submittals_v2 (structured per-item SubmittalSet from the unified resolver) per rule.

Input Schema

Name	Required	Description
`limit`	No	Max results (default 10 — rules are ~1K tokens each)
`address`	No	Full street address — when provided, each result row also includes `submittals_v2` from the unified resolver (per-item triggers, source citations, filler actor).
`keyword`	No	Keyword in project type, trigger, thresholds, or notes (e.g. "deck", "adu", "egress")
`jurisdiction`	No	Jurisdiction slug or display name (e.g. "seattle", "bellevue", "tacoma")
`onlyAuthoritative`	No	Default true: return only 'authoritative' and 'wa-baseline' rules, the two tiers Kolmo's city pages show. Kept for compatibility: no other tier is held, so false returns the same rules.

Output Schema

Name	Required	Description	Default
`parcel`	No
`matched`	Yes
`results`	No
`returned`	Yes
`disclaimer`	Yes
`totalRules`	Yes
`attribution`	Yes
`authoritativeRules`	Yes
`jurisdictionsWithAuthoritativeCoverage`	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."

Changed1 schema field changedOct 14, 2026

changedInput schema / properties / onlyAuthoritative / description

Previous value: -"Default true: return only 'authoritative' and 'wa-baseline' rules. Set false to also return every other tier, including 'web-fetched' rows — these are published but deliberately not shown on Kolmo's city pages, and their cited source is not verified to state the rule. Prefer the default."New value: +"Default true: return only 'authoritative' and 'wa-baseline' rules, the two tiers Kolmo's city pages show. Kept for compatibility: no other tier is held, so false returns the same rules."

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
```
Changed7 schema fields changedSep 3, 2026
- changedInput schema / properties / limit / description
```
Previous value: -"Max results (default 50)"New value: +"Max results (default 10 — rules are ~1K tokens each)"
```
- 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": {
+    "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"
+    },
+    "authoritativeRules": {
+      "type": "number"
+    },
+    "disclaimer": {
+      "type": "string"
+    },
+    "jurisdictionsWithAuthoritativeCoverage": {},
+    "matched": {
+      "type": "number"
+    },
+    "parcel": {},
+    "results": {},
+    "returned": {
+      "type": "number"
+    },
+    "totalRules": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "totalRules",
+    "authoritativeRules",
+    "matched",
+    "returned",
+    "disclaimer",
+    "attribution"
+  ],
+  "type": "object"
+}

Changed1 schema field changedAug 22, 2026

changedInput schema / properties / onlyAuthoritative / description

Previous value: -"If true, exclude legacy LLM-seeded rows. Default true."New value: +"Default true: return only 'authoritative' and 'wa-baseline' rules. Set false to also return every other tier, including 'web-fetched' rows — these are published but deliberately not shown on Kolmo's city pages, and their cited source is not verified to state the rule. Prefer the default."

Changed1 schema field changedMay 17, 2026

addedInput schema / properties / address

Added value: +{
+  "description": "Full street address — when provided, each result row also includes `submittals_v2` from the unified resolver (per-item triggers, source citations, filler actor).",
+  "type": "string"
+}

Changed4 schema fields changedApr 27, 2026

changedInput schema / properties / jurisdiction / description

Previous value: -"Filter by jurisdiction (e.g. \"Seattle\", \"Bellevue\", \"King County\")"New value: +"Jurisdiction slug or display name (e.g. \"seattle\", \"bellevue\", \"tacoma\")"

changedInput schema / properties / keyword / description

Previous value: -"Keyword in trigger text or notes (e.g. \"deck\", \"ADU\", \"electrical\")"New value: +"Keyword in project type, trigger, thresholds, or notes (e.g. \"deck\", \"adu\", \"egress\")"

changedInput schema / properties / limit / description

Previous value: -"Max results (default 100)"New value: +"Max results (default 50)"

addedInput schema / properties / onlyAuthoritative

Added value: +{
+  "description": "If true, exclude legacy LLM-seeded rows. Default true.",
+  "type": "boolean"
+}

AddedApr 22, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuine behavioral context beyond that: results are enriched conditionally when `address` is supplied, pulling `submittals_v2` from the unified resolver. It does not mention auth, rate limits or whether the resolver is expensive to call.

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?

Three sentences, front-loaded with the operation and the detail payload, then filtering, then the conditional `address` enrichment. The closest thing to waste is the `submittals_v2` sentence, which repeats what the schema already says about the `address` parameter.

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, so return values need not be explained, and the description still flags the one conditional shape change (per-rule submittals_v2). What is missing is routing guidance against the crowded set of permit-related siblings, which matters for a tool with five optional filters and no required parameters.

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 the schema already explains limit defaults, keyword scope, jurisdiction slug format, the address-driven submittals_v2 enrichment and the onlyAuthoritative compatibility note. The description largely restates the address/submittals_v2 behavior and the slug-or-keyword filtering rather than adding semantics beyond the schema, so the baseline of 3 applies.

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?

The description opens with a specific verb and resource ("Enumerate permit rules") and enumerates the detail payload: timeline, fee model, inspection sequence, submittals, contractor specialties. That is much clearer than a bare name restatement, but it never distinguishes itself from near-duplicate siblings such as check_permit_requirements, answer_permit_question or resolve_permit_submittals.

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?

It supplies two concrete example intents ("what does a Seattle ADU permit require?" and "list all rules for a jurisdiction"), which implies when to reach for it. However, the first example is exactly the kind of natural-language question answer_permit_question appears built for, and the description never says when NOT to use this tool or which sibling to prefer.

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

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

Resources

Need Help?