Kolmo Construction

Business info & credentials

get_business_info

Read-onlyIdempotent

Get Kolmo Construction company information: contact details, hours, service area, specializations, and tools.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`name`	Yes
`email`	Yes
`hours`	No
`phone`	Yes
`tools`	Yes
`rating`	Yes
`address`	Yes
`founded`	No
`license`	Yes
`website`	Yes
`attribution`	Yes
`serviceArea`	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.
`notCertified`	Yes	Set-asides Kolmo does NOT hold. Never infer one that appears here.
`serviceRegion`	Yes	Where Kolmo takes work. This decides coverage, not serviceArea.
`certifications`	Yes
`specializations`	Yes	Trades Kolmo performs. Not all of these have a service page — check list_services before linking one.
`federalRegistration`	Yes
`personnelQualifications`	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
- 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 / rating / additionalProperties
```
Removed value: -true
```

Changed3 schema fields changedSep 16, 2026

addedOutput schema / properties / serviceArea / 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: +{
+  "description": "Where Kolmo takes work. This decides coverage, not serviceArea.",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "name",
-  "license",
-  "phone",
-  "email",
-  "website",
-  "address",
-  "rating",
-  "serviceArea",
-  "certifications",
-  "personnelQualifications",
-  "federalRegistration",
-  "notCertified",
-  "specializations",
-  "tools",
-  "attribution"
-]New value: +[
+  "name",
+  "license",
+  "phone",
+  "email",
+  "website",
+  "address",
+  "rating",
+  "serviceRegion",
+  "serviceArea",
+  "certifications",
+  "personnelQualifications",
+  "federalRegistration",
+  "notCertified",
+  "specializations",
+  "tools",
+  "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": {
+    "address": {
+      "type": "string"
+    },
+    "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"
+    },
+    "certifications": {
+      "additionalProperties": {},
+      "type": "object"
+    },
+    "email": {
+      "type": "string"
+    },
+    "federalRegistration": {
+      "additionalProperties": {},
+      "type": "object"
+    },
+    "founded": {},
+    "hours": {},
+    "license": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "notCertified": {
+      "description": "Set-asides Kolmo does NOT hold. Never infer one that appears here.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "personnelQualifications": {
+      "additionalProperties": {},
+      "type": "object"
+    },
+    "phone": {
+      "type": "string"
+    },
+    "rating": {
+      "additionalProperties": true,
+      "properties": {
+        "reviewCount": {},
+        "source": {
+          "type": "string"
+        },
+        "value": {}
+      },
+      "required": [
+        "source"
+      ],
+      "type": "object"
+    },
+    "serviceArea": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "specializations": {
+      "description": "Trades Kolmo performs. Not all of these have a service page — check list_services before linking one.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "tools": {
+      "additionalProperties": {},
+      "type": "object"
+    },
+    "website": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "license",
+    "phone",
+    "email",
+    "website",
+    "address",
+    "rating",
+    "serviceArea",
+    "certifications",
+    "personnelQualifications",
+    "federalRegistration",
+    "notCertified",
+    "specializations",
+    "tools",
+    "attribution"
+  ],
+  "type": "object"
+}

First observedApr 13, 2026

TDQS

B3.2/5.0

Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds nothing behavioral beyond that — it restates what the tool returns rather than disclosing anything like data freshness or scope limits, which matters given the openWorld hint.

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?

One compact sentence with the resource front-loaded and zero filler. The enumerate list is efficient, though it flattens distinct concerns (contact info vs. tools) into a single clause.

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?

With no inputs, a rich annotation set, and an existing output schema that documents the return shape, the description does not need to explain results. The only real gap is the lack of routing guidance among the large sibling set that overlaps with pieces of this payload.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The listed content areas are effectively the (parameter-less) response surface.

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?

Names a specific verb and resource ('Get Kolmo Construction company information') and enumerates the payload (contact details, hours, service area, specializations, tools), which lets an agent recognize it as the general company-profile tool. It stops short of explicitly contrasting itself with content-adjacent siblings such as check_service_area_coverage or get_service.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool, when not to, or which sibling to prefer — notably nothing distinguishing the 'service area' string returned here from check_service_area_coverage, or 'specializations' from list_services. Usage must be entirely inferred from the content list.

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?