kolmo-mcp-server

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

TableJSON Schema

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

Output Schema

TableJSON 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.

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.5/5.0

Behavior5/5

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

Annotations already declare read-only and idempotent behavior, and the description adds valuable operational semantics: unconfirmed places should be treated as in-area, out_of_area is the only refusal signal, and a count of completed projects is also returned. This goes well beyond the structured annotations.

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 compact and front-loaded with the core purpose, then follows with the decision-relevant coverage values and the extra count return. Every sentence carries necessary information with no filler.

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?

Given the output schema exists and annotations cover safety, the description sufficiently explains the valid response categories, the handling of unrecognized places, and the additional project count. It gives an agent everything needed to invoke the tool and act on the result.

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 schema already provides 100% coverage for the single `location` parameter, including examples. The description reinforces that the location can be a city, neighborhood, ZIP, or address, but does not add significant new meaning beyond the schema's own description.

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 opens with a specific action and resource: 'Check whether Kolmo takes work in a given city, neighborhood, ZIP or address.' It names the exact geographic scope (Washington, Puget Sound core) and the distinct return categories, making it clear how this tool differs from siblings like get_business_info or lookup_parcel_by_address.

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 provides strong context on how to interpret results: primary, nearby, case_by_case, unconfirmed, and out_of_area, including the critical note that out_of_area is the only negative value. It does not explicitly name alternative tools or give when-not-to-use conditions, so it falls just short of a 5.

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.