Kolmo Construction

Contractor-to-permit specialty match

match_contractor_to_permit

Read-onlyIdempotent

Cross-reference a WA contractor's L&I license specialty against a permit's required specialties. Returns whether the contractor is qualified to pull/work the permit, with explicit gap callouts (e.g. "missing electrical specialty 02"). Combines real-time L&I data with Kolmo's authoritative permit catalog.

Input Schema

TableJSON Schema

Name	Required	Description
`projectType`	Yes	Canonical project type (kitchen, bathroom, basement, deck, fence, siding, windows, flooring, adu, roofing, hvac, electrical, plumbing, addition)
`contractorQuery`	Yes	Contractor license number, business name, UBI or phone number
`jurisdictionSlug`	Yes	Permit jurisdiction slug (e.g. "seattle", "tacoma")

Output Schema

TableJSON Schema

Name	Required	Description
`match`	Yes	null: no single contractor could be identified from contractorQuery, so no comparison was made — not a finding either way.
`checks`	No
`permit`	No
`reason`	No
`missing`	No
`sourceUrl`	No
`verifyUrl`	No
`candidates`	No
`contractor`	No
`attribution`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 22, 2026

changedInput schema / properties / contractorQuery / description

Previous value: -"Contractor license number or business name"New value: +"Contractor license number, business name, UBI or phone number"

addedOutput schema / properties / candidates
```
Added value: +{}
```

addedOutput schema / properties / match / description

Added value: +"null: no single contractor could be identified from contractorQuery, so no comparison was made — not a finding either way."

changedOutput schema / properties / match / type

Previous value: -"boolean"New value: +[
+  "boolean",
+  "null"
+]

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": {
+    "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"
+    },
+    "checks": {},
+    "contractor": {},
+    "match": {
+      "type": "boolean"
+    },
+    "missing": {},
+    "permit": {},
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "sourceUrl": {},
+    "verifyUrl": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "match"
+  ],
+  "type": "object"
+}

AddedApr 27, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive, so the safety profile is covered. The description adds value by explaining data sources (real-time L&I and Kolmo's catalog) and the nature of the output (gap callouts). No contradictions with annotations are present.

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 three sentences, with the primary action first, followed by output specification and data source context. Every sentence contributes meaning without redundancy. The structure is front-loaded and efficient, leaving no unnecessary words.

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?

The description covers the purpose, output, and data sources. It does not explicitly address edge cases (e.g., missing license, permit with no required specialties) or error handling, but the presence of an output schema (stated) likely covers those. For a read-only, idempotent tool with clear parameters and output, this is adequately complete for an agent to invoke correctly.

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 documents all parameters (contractorQuery, jurisdictionSlug, projectType) with clear examples. The description does not add additional parameter-level detail beyond the schema, but it reinforces the purpose of the parameters in the context of specialty matching. The baseline of 3 is appropriate because the schema does the heavy lifting.

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 precise action: cross-referencing a contractor's L&I specialty against a permit's required specialties. It clearly distinguishes itself from siblings like check_contractor_license_status (which checks license validity) and check_permit_requirements (which lists requirements) by focusing on the matching outcome. The output is explicit: qualification status with gap callouts.

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 implies a clear use case: determining if a specific contractor is qualified for a specific permit. It does not explicitly name alternatives or exclusions, but the specificity of 'contractor to permit' matching makes it obvious when to use this tool over siblings. The mention of real-time L&I data and Kolmo's catalog provides context but no explicit when-not guidance.

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?