Kolmo Construction

Service-area coverage

check_service_area_coverage

Read-onlyIdempotent

Check whether Kolmo takes work in a given city, neighborhood, ZIP or address. Kolmo works across Washington: Puget Sound (Bellingham to Olympia) is the core area and the rest of the state is case by case. coverage is primary (a featured city or Seattle neighborhood), nearby (in the core area), case_by_case (Washington, outside Puget Sound), unconfirmed (not a place this check recognizes: treat it as in area) or out_of_area (outside Washington, the ONLY value that means Kolmo does not take the work). Follow guidance. Also returns the count of completed projects in or near that location.

Input Schema

Name	Required	Description	Default
`location`	Yes	City, neighborhood, ZIP or address to check, e.g. "Ballard", "Normandy Park", "98105", "Tacoma"

Output Schema

Name	Required	Description
`query`	No
`verdict`	No
`coverage`	Yes
`takesWork`	Yes	False only when the place is outside Washington.
`contactUrl`	Yes
`attribution`	Yes
`matchedCity`	No
`serviceCities`	Yes	Featured cities with their own landing pages. NOT the service area boundary: a place missing from this list is not out of area. See serviceRegion.
`serviceRegion`	Yes
`nearbyProjectCount`	Yes
`matchedNeighborhood`	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."

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

Changed9 schema fields changedSep 16, 2026

changedInput schema / properties / location / description

Previous value: -"City, neighborhood, or ZIP to check, e.g. \"Ballard\", \"Bellevue\", \"98105\", \"Tacoma\""New value: +"City, neighborhood, ZIP or address to check, e.g. \"Ballard\", \"Normandy Park\", \"98105\", \"Tacoma\""

addedOutput schema / properties / coverage / enum

Added value: +[
+  "primary",
+  "nearby",
+  "case_by_case",
+  "unconfirmed",
+  "out_of_area"
+]

addedOutput schema / properties / coverage / type
```
Added value: +"string"
```
removedOutput schema / properties / primaryCounty
```
Removed value: -{}
```
removedOutput schema / properties / radiusKm
```
Removed value: -{
-  "type": "number"
-}
```

addedOutput schema / properties / serviceCities / description

Added value: +"Featured cities with their own landing pages. NOT the service area boundary: a place missing from this list is not out of area. See serviceRegion."

addedOutput schema / properties / serviceRegion
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / takesWork

Added value: +{
+  "description": "False only when the place is outside Washington.",
+  "type": "boolean"
+}

changedOutput schema / required

Previous value: -[
-  "radiusKm",
-  "serviceCities",
-  "nearbyProjectCount",
-  "contactUrl",
-  "attribution"
-]New value: +[
+  "coverage",
+  "takesWork",
+  "serviceRegion",
+  "serviceCities",
+  "nearbyProjectCount",
+  "contactUrl",
+  "attribution"
+]

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"
+    },
+    "contactUrl": {
+      "type": "string"
+    },
+    "coverage": {},
+    "matchedCity": {},
+    "matchedNeighborhood": {},
+    "nearbyProjectCount": {
+      "type": "number"
+    },
+    "primaryCounty": {},
+    "query": {},
+    "radiusKm": {
+      "type": "number"
+    },
+    "serviceCities": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "verdict": {}
+  },
+  "required": [
+    "radiusKm",
+    "serviceCities",
+    "nearbyProjectCount",
+    "contactUrl",
+    "attribution"
+  ],
+  "type": "object"
+}

AddedApr 22, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations, the description explains the meaning of each coverage result, how unconfirmed should be treated, and that only out_of_area is a negative result. It also discloses that the tool returns a count of completed projects in or near the location, adding useful behavioral context.

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 description is front-loaded and appropriately sized for a one-parameter read tool. It is slightly dense and includes an ambiguous instruction to 'Follow `guidance`,' but most sentences carry meaningful information.

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 tool is simple, has a fully described single parameter, annotations covering safety, and an output schema. The description still adds enough about result interpretation and the project count that an agent can call and use it 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 coverage is 100% and the single location parameter already documents accepted examples such as city, neighborhood, ZIP, and address. The description restates those input types but adds no additional parameter-specific syntax or constraints.

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 specific verb and resource: checking whether Kolmo takes work in a given location. It also defines the exact coverage taxonomy, making the tool's purpose precise and distinguishable from all sibling lookup tools.

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?

It clearly frames the tool as the coverage check for a city, neighborhood, ZIP, or address, and explicitly warns that out_of_area is the only value meaning Kolmo does not take the work. It does not name alternate tools or when not to use this one, but the context is otherwise clear.

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?