Kolmo Construction

Permit jurisdiction coverage

list_permit_jurisdictions

Read-onlyIdempotent

List the jurisdictions in Kolmo's permit catalog (King, Pierce, Snohomish counties). Compact by default — results is keyed by county (King / Pierce / Snohomish), each a list of {slug, name, verified} — the whole catalogue in one call (~4K tokens), enough to pick a jurisdictionSlug for estimate_permit_fee, check_permit_requirements or get_permit_rule_details. Pass slug for one jurisdiction's full record (department, fee-schedule URL, phone, code cycles, notes), or detail: true for full records on every row.

Input Schema

Name	Required	Description
`slug`	No	One jurisdiction by slug, e.g. "bellevue" or "mercer-island". Returns its full record.
`county`	No	Filter by county
`detail`	No	If true, every row carries the full record. Default false (compact rows). The full catalogue in detail is ~9x larger — prefer `slug` when you need one city.
`verifiedOnly`	No	If true, only return rows where portal_url is populated (verified from official source). Default false.

Output Schema

Name	Required	Description	Default
`total`	Yes
`detail`	Yes
`results`	No
`attribution`	Yes

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
```

Changed10 schema fields changedSep 3, 2026

addedInput schema / properties / detail

Added value: +{
+  "description": "If true, every row carries the full record. Default false (compact rows). The full catalogue in detail is ~9x larger — prefer `slug` when you need one city.",
+  "type": "boolean"
+}

addedInput schema / properties / slug

Added value: +{
+  "description": "One jurisdiction by slug, e.g. \"bellevue\" or \"mercer-island\". Returns its full record.",
+  "type": "string"
+}

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 / detail
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / required

Previous value: -[
-  "total",
-  "attribution"
-]New value: +[
+  "total",
+  "detail",
+  "attribution"
+]

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"
+    },
+    "results": {},
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "attribution"
+  ],
+  "type": "object"
+}

AddedApr 27, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare this a safe, idempotent read; the description goes well beyond them by disclosing payload size (~4K tokens), the response shape ('results keyed by county... each a list of {slug, name, verified}'), and the amplification factor for `detail`. That is exactly the cost/scale information an agent needs before choosing a fan-out option.

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?

Front-loaded with purpose and default behavior, then the expansion options in the order an agent would consider them. The parentheticals (county list, returned record fields) carry real information rather than filler; no sentence is redundant with the schema.

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?

Despite having an output schema (so return values could be omitted), the description still summarizes the compact shape and gives the cost of broadening it. With zero required parameters and four optional ones, an agent has everything needed to call this correctly on the first try.

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%, so baseline is 3, and the description earns one above it by explaining what `slug` actually returns ('one jurisdiction's full record (department, fee-schedule URL, phone, code cycles, notes)') and quantifying the token tradeoff for `detail`. `county` and `verifiedOnly` are left entirely to the schema, which is acceptable at full coverage but keeps it off a 5.

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 and resource ('List the jurisdictions in Kolmo's permit catalog') and immediately scopes it with the three concrete counties. It also distinguishes itself from siblings by naming the exact tools whose jurisdictionSlug input this list feeds (estimate_permit_fee, check_permit_requirements, get_permit_rule_details).

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?

Explicitly frames the default (whole catalogue in one call) as the right choice for picking a slug, then gives two named alternatives -- `slug` for one city, `detail: true` for everything -- with a stated cost penalty ('~9x larger') and a recommendation ('prefer `slug` when you need one city'). When-to-use and when-not-to-use are both present.

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?