kolmo-mcp-server

WA contractor license status

check_contractor_license_status

Read-onlyIdempotent

Look up any Washington State contractor's license, bond, and insurance status using public L&I data (updated daily). Works for Kolmo or any competitor. Great for verifying a contractor before hiring — checks if they are licensed, bonded, and insured in WA. Search by license number, business name, UBI, or phone number. Results are ranked closest match first; when identified is false, several businesses match and none should be reported as the contractor.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	Contractor license number (e.g. "KOLMOL*753JS"), business name (e.g. "Kolmo LLC"), 9-digit UBI, or phone number

Output Schema

TableJSON Schema

Name	Required	Description
`next`	No
`note`	No
`found`	Yes	false means L&I holds no matching record — a real answer, not a lookup failure.
`query`	Yes
`message`	No
`results`	No
`verifyUrl`	No
`identified`	No	true: the top results are one business. false: several businesses match, or only part of the name did — do not report any result as the contractor asked about.
`searchedBy`	No	license-number, ubi, phone, trade-name or business-name
`attribution`	No
`moreMatches`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 22, 2026

changedInput schema / properties / query / description

Previous value: -"Contractor license number (e.g. \"KOLMOL*753JS\") or business name (e.g. \"Kolmo Construction\")"New value: +"Contractor license number (e.g. \"KOLMOL*753JS\"), business name (e.g. \"Kolmo LLC\"), 9-digit UBI, or phone number"

addedOutput schema / properties / identified

Added value: +{
+  "description": "true: the top results are one business. false: several businesses match, or only part of the name did — do not report any result as the contractor asked about.",
+  "type": "boolean"
+}

addedOutput schema / properties / moreMatches
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / note
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / searchedBy

Added value: +{
+  "description": "license-number, ubi, phone, trade-name or business-name",
+  "type": "string"
+}

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"
+    },
+    "found": {
+      "description": "false means L&I holds no matching record — a real answer, not a lookup failure.",
+      "type": "boolean"
+    },
+    "message": {
+      "type": "string"
+    },
+    "next": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "query": {
+      "type": "string"
+    },
+    "results": {},
+    "verifyUrl": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "found",
+    "query"
+  ],
+  "type": "object"
+}

First observedApr 14, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, etc.), the description discloses that data is updated daily, results are ranked closest match first, and when `identified` is false, no match should be reported. This is critical behavioral guidance about how to handle ambiguous results, which adds significant value.

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?

The core purpose is front-loaded in the first sentence. The additional sentences provide useful context about use case, search inputs, and result ambiguity. There is minor redundancy ('checks if they are licensed, bonded, and insured' repeats the first sentence), but overall it is sufficiently concise.

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?

The description covers the essential operational aspects: scope (WA), data source and freshness, accepted query types, and the critical ambiguity handling rule. With an output schema present, an agent has all necessary context to invoke the tool and interpret results 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?

The input schema already fully describes the query parameter with examples and accepted formats (license number, business name, UBI, phone). The description essentially repeats this information without adding new meaning, so the baseline of 3 applies given 100% schema coverage.

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 uses a specific verb ('Look up') and a specific resource ('Washington State contractor's license, bond, and insurance status'). It also clarifies that it works for any competitor and explicitly names the checks (licensed, bonded, insured in WA), which differentiates it from siblings like get_business_info or match_contractor_to_permit.

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 gives a clear use case ('Great for verifying a contractor before hiring') and lists the accepted search terms and result ranking. It does not explicitly name alternative tools or state when not to use this tool, so it stops short of a full when/when-not guideline.

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.