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

TableJSON Schema

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

Output Schema

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

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

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well-covered. The description adds no additional behavioral detail beyond the fact that it returns IDs, but it does not contradict the 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 two sentences with no filler. The first sentence states the core function with concrete examples, and the second sentence gives the practical downstream use, earning its place by connecting this tool to get_estimate.

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?

For a single-parameter, read-only lookup tool with a rich enum and an output schema, the description is complete. It explains what is returned, gives representative coverage across project types, and tells the agent how the result should be used.

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%, with a clear description and enum for projectType, so the schema carries the parameter documentation burden. The description adds contextual examples of material categories but no additional parameter semantics beyond what the schema already provides.

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 uses a specific verb and resource combination ('Get available material choices for a project type') and elaborates with concrete examples like flooring types, paint grades, and decking materials. It also distinguishes this tool by tying it to get_estimate, which differentiates it from sibling tools such as get_material_catalog.

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?

The description provides clear context by stating that returned IDs should be used in the project fields of get_estimate, giving agents a concrete downstream purpose. It does not explicitly state when not to use this tool or name alternative tools, so it stops 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 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?