Kolmo Construction

Completed project portfolio

list_projects

Read-onlyIdempotent

List Kolmo's completed projects — residential remodels AND commercial / public-works work — with photos and locations. Filter by category or keyword; get_project has the full case study. Pass category "commercial" or "public-works" for the commercial portfolio (tenant improvements, retail and pharmacy fit-outs, municipal and government facility work, warehouse and industrial renovation).

Input Schema

Name	Required	Description
`limit`	No	Max results (default 10)
`offset`	No	Pagination offset (default 0)
`search`	No	Filter by keyword in project title, description, or location
`category`	No	Filter. Residential: kitchen, bathroom, full-home, outdoor, garage, basement. Commercial: commercial, public-works.

Output Schema

Name	Required	Description	Default
`limit`	Yes
`total`	Yes
`hubUrl`	Yes
`offset`	Yes
`results`	Yes
`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."

Changed6 schema fields changedOct 10, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- changedInput schema / properties / limit / description
```
Previous value: -"Max results (default 20)"New value: +"Max results (default 10)"
```
- 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
```
- removedOutput schema / properties / results / items / additionalProperties
```
Removed value: -true
```

Changed1 schema field changedSep 14, 2026

changedInput schema / properties / category / description

Previous value: -"Filter. Residential: kitchen, bathroom, full-home, outdoor, basement. Commercial: commercial, public-works."New value: +"Filter. Residential: kitchen, bathroom, full-home, outdoor, garage, basement. Commercial: commercial, public-works."

Changed1 schema field changedSep 5, 2026

changedInput schema / properties / category / description

Previous value: -"Filter: kitchen, bathroom, full-home, outdoor, basement"New value: +"Filter. Residential: kitchen, bathroom, full-home, outdoor, basement. Commercial: commercial, public-works."

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"
+    },
+    "hubUrl": {
+      "type": "string"
+    },
+    "limit": {
+      "type": "number"
+    },
+    "offset": {
+      "type": "number"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "category": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "completedAt": {},
+          "description": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "imageAfter": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "imageBefore": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "location": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "slug": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "offset",
+    "limit",
+    "results",
+    "hubUrl",
+    "attribution"
+  ],
+  "type": "object"
+}

First observedApr 13, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so the bar is lower. The description still adds value by disclosing result payload contents (photos and locations) and the breadth of the portfolio. It says nothing about pagination defaults, but the schema covers limit/offset.

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?

Three front-loaded sentences: purpose first, then filtering and the sibling alternative, then category guidance. The long parenthetical of commercial sub-types is dense but functional; nothing is redundant with the schema.

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?

An output schema exists, so return values need not be explained, and the two-property mutation surface is trivial. Combined with full annotations and full schema coverage, the description supplies everything needed to call it correctly; only pagination expectations are left implicit.

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, but the description goes beyond it by unpacking what 'commercial' and 'public-works' actually encompass (tenant improvements, retail/pharmacy fit-outs, municipal work, warehouse renovation) — meaning an agent cannot get from the schema's bare enum-style list.

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 Kolmo's completed projects'), names the two scopes it spans (residential remodels and commercial/public-works), and notes what comes back (photos, locations). It also explicitly separates itself from get_project, so an agent can route without opening a schema.

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?

Tells the agent to filter by category or keyword, and explicitly points to get_project for the full case study — a named alternative with a clear condition. It also instructs which category values select the commercial portfolio, though it gives no when-not-to-use guidance beyond that.

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?