kolmo-mcp-server

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. Pass category "commercial" or "public-works" for the commercial portfolio (tenant improvements, retail and pharmacy fit-outs, municipal and government facility work, ADA remediation, warehouse and industrial renovation).

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results (default 20)
`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

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

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 14, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the safety profile is covered. The description adds useful domain context: what the commercial/public-works bucket actually contains (tenant improvements, fit-outs, ADA remediation), which shapes what the agent will get back. It does not mention pagination defaults despite them existing, which keeps it from a 5.

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?

Purpose and scope are front-loaded in the first sentence, and the category semantics follow in support. It's slightly dense in the final clause but every sentence earns its place; nothing is redundant 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?

With an output schema present, return-value explanation is unnecessary, and the annotations cover the safety profile. For a filterable list tool with fully documented params, the description supplies exactly the missing domain interpretation and nothing an agent needs is absent.

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 already 100%, so the baseline is 3. The description goes further by interpreting the category parameter for the agent — mapping 'commercial'/'public-works' to the real-world content types it will return and naming the residential options' domain — adding meaning beyond the raw enum list in the schema.

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?

Specific verb+resource: 'List Kolmo's completed projects' with explicit scope (residential AND commercial/public-works). It carves out a distinct niche apart from get_project (singular lookup) and list_project_types, and the category routing makes the tool's identity unambiguous.

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?

Gives a clear trigger condition — call it to browse completed work by category or keyword — and spells out which category values drive the commercial portfolio. It never states when NOT to use it (e.g., single-project retrieval via get_project), so it stops short of the 5-level explicit alternatives framing.

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.