Kolmo Construction

Material options by project type

get_material_options

Read-onlyIdempotent

Get available material choices for a project type — flooring types, paint grades, decking materials, kitchen/bath/basement/ADU scope tiers, ADA modifications, etc. Use the returned IDs in the project fields of get_estimate.

Input Schema

Name	Required	Description	Default
`projectType`	Yes	The project type to list materials for

Output Schema

Name	Required	Description
`options`	No	Shape varies by project type — an array of {id,name,costPerUnit,unit} for the material-driven types, a keyed catalog for the scope-driven ones (kitchen, bathroom, basement, adu, ada).
`attribution`	Yes
`projectType`	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."

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

Changed1 schema field changedSep 15, 2026

changedInput schema / properties / projectType / enum

Previous value: -[
-  "interior-painting",
-  "exterior-painting",
-  "flooring",
-  "deck",
-  "windows",
-  "siding",
-  "fence",
-  "landscaping",
-  "kitchen",
-  "bathroom",
-  "basement",
-  "adu",
-  "ada",
-  "electrical",
-  "plumbing",
-  "garage-doors",
-  "concrete",
-  "insulation",
-  "gutters"
-]New value: +[
+  "interior-painting",
+  "exterior-painting",
+  "flooring",
+  "deck",
+  "windows",
+  "siding",
+  "fence",
+  "landscaping",
+  "kitchen",
+  "bathroom",
+  "basement",
+  "adu",
+  "ada",
+  "electrical",
+  "plumbing",
+  "garage-doors",
+  "doors",
+  "concrete",
+  "insulation",
+  "gutters"
+]

Changed1 schema field changedSep 15, 2026

changedInput schema / properties / projectType / enum

Previous value: -[
-  "interior-painting",
-  "exterior-painting",
-  "flooring",
-  "deck",
-  "windows",
-  "siding",
-  "fence",
-  "landscaping",
-  "kitchen",
-  "bathroom",
-  "basement",
-  "adu",
-  "ada"
-]New value: +[
+  "interior-painting",
+  "exterior-painting",
+  "flooring",
+  "deck",
+  "windows",
+  "siding",
+  "fence",
+  "landscaping",
+  "kitchen",
+  "bathroom",
+  "basement",
+  "adu",
+  "ada",
+  "electrical",
+  "plumbing",
+  "garage-doors",
+  "concrete",
+  "insulation",
+  "gutters"
+]

Changed2 schema fields changedSep 6, 2026

changedInput schema / properties / projectType / enum

Previous value: -[
-  "interior-painting",
-  "deck",
-  "exterior-painting",
-  "flooring",
-  "windows",
-  "siding",
-  "fence",
-  "landscaping",
-  "kitchen",
-  "bathroom",
-  "ada"
-]New value: +[
+  "interior-painting",
+  "exterior-painting",
+  "flooring",
+  "deck",
+  "windows",
+  "siding",
+  "fence",
+  "landscaping",
+  "kitchen",
+  "bathroom",
+  "basement",
+  "adu",
+  "ada"
+]

changedOutput schema / properties / options / description

Previous value: -"Shape varies by project type — an array of {id,name,costPerUnit,unit} for most, a keyed catalog for kitchen/bathroom/ada."New value: +"Shape varies by project type — an array of {id,name,costPerUnit,unit} for the material-driven types, a keyed catalog for the scope-driven ones (kitchen, bathroom, basement, adu, ada)."

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"
+    },
+    "options": {
+      "description": "Shape varies by project type — an array of {id,name,costPerUnit,unit} for most, a keyed catalog for kitchen/bathroom/ada."
+    },
+    "projectType": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "projectType",
+    "attribution"
+  ],
+  "type": "object"
+}

First observedApr 13, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered elsewhere. The description's added value is the output-consumption contract (IDs feed get_estimate) and the breadth of category coverage, but it says nothing about output shape or ordering — acceptable since an output schema exists, yet not much beyond the minimum.

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?

Two sentences, zero waste. The category list is front-loaded to establish scope, and the get_estimate handoff follows immediately as the actionable instruction.

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?

One fully-documented enum param, an output schema, and annotations covering the safety profile mean the description needs only to establish purpose and downstream wiring, which it does. The remaining gap is disambiguation from get_material_catalog, which an agent may reasonably confuse with this tool.

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 description coverage is 100% and the single parameter has a 20-value enum, so the schema already carries the meaning. The description's category examples ('kitchen/bath/basement/ADU scope tiers, ADA modifications') loosely hint at the enum surface but add no format or selection guidance beyond it — baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get available material choices') scoped by project type, and enumerates concrete categories (flooring, paint grades, decking, scope tiers, ADA) that make the payload concrete. It does not, however, distinguish itself from the similarly-named sibling get_material_catalog, leaving an agent to guess which one to call.

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 explicit downstream usage ('Use the returned IDs in the project fields of get_estimate'), which is exactly the kind of routing guidance an agent needs. It stops short of naming an exclusion or alternative — notably nothing says when to prefer get_material_catalog over this tool.

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?