Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.kolmo.www/kolmo-mcp-server

REMOTE · WWW.KOLMO.IO · SCANNED AUG 3

Seattle GC (SEDBE #D700031098). Residential & public works: estimates, ROI, permits, quotes.

Available components

+4 this week 70 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability80
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 5479 tokens (~152/item across 36 items; 36 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · www.kolmo.io

# add to Claude Code
claude mcp add --transport http io-kolmo-www-kolmo-mcp-server https://www.kolmo.io/mcp
# ~/.codex/config.toml
[mcp_servers.io-kolmo-www-kolmo-mcp-server]
url = "https://www.kolmo.io/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-kolmo-www-kolmo-mcp-server": {
      "type": "remote",
      "url": "https://www.kolmo.io/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-kolmo-www-kolmo-mcp-server --url https://www.kolmo.io/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-kolmo-www-kolmo-mcp-server:
    url: "https://www.kolmo.io/mcp"
// mcp.json
{
  "mcpServers": {
    "io-kolmo-www-kolmo-mcp-server": {
      "type": "http",
      "url": "https://www.kolmo.io/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 66

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://www.kolmo.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=kolmo.io CN=WE1,O=Google Trust Services,C=US 19 Jun 2026 17 Sept 2026 ECDSA 256 ECDSA-SHA256 34328069b6096e8413d2da6e33f28431
SANs: kolmo.io, *.kolmo.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b
DNSSEC insecure

Validation of www.kolmo.io. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
kolmo.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.kolmo.io/mcp Verified 200
http (plaintext) http://www.kolmo.io/mcp HTTPS enforced 301 https://www.kolmo.io/mcp
MCP tools — 36 exposed · ~5,479 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
answer_permit_question ~153

Grounded permit Q&A for a specific Seattle-area address. Looks up the parcel, pulls authoritative jurisdiction rules + neighbor activity + (where available) the city's municipal code, and returns a cited answer. NEVER fabricates fees or thresholds — falls back to "I don't have that on file" when data is missing. Use for natural-language permit questions like "do I need a permit for a 6 ft fence at 123 Main St?" or "what permits does an ADU at this address require?"

NameTypeReqDescription
addressstringyesFull street address in King, Pierce, or Snohomish County, WA
questionstringyesA single permit/zoning/setback/overlay question about this parcel

No output schema declared.

No examples provided.

check_contractor_license_status ~97

Look up any Washington State contractor's license, bond, and insurance status using public L&I data (updated daily). Works for Kolmo or any competitor. Great for verifying a contractor before hiring — checks if they are licensed, bonded, and insured in WA.

NameTypeReqDescription
querystringyesContractor license number (e.g. "KOLMOL*753JS") or business name (e.g. "Kolmo Construction")

No output schema declared.

No examples provided.

check_permit_requirements ~255

Check whether a residential construction project in King/Pierce/Snohomish counties requires a permit. Returns timeline, fee notes, inspection sequence, required submittals, and official source URL — preferring jurisdiction-verified rules. Use for "Do I need a permit to build a deck in Seattle?" or "What permits are required for a kitchen remodel in Bellevue?". Pass `address` to also receive the structured per-item SubmittalSet (`submittals_v2`) from the unified permit engine — Seattle is full SDCI fidelity, other 9 verified cities are wa-baseline-stub.

NameTypeReqDescription
addressstringFull street address — when provided, the response includes `submittals_v2` from the unified resolver (per-item triggers, source citations, filler actor). Overrides `location` for jurisdiction routing.
locationstringCity or jurisdiction slug, e.g. "Seattle", "Bellevue", "Tacoma", "king-county-unincorporated"
projectTypestringProject type — canonical: kitchen, bathroom, basement, deck, fence, siding, windows, flooring, adu, roofing, hvac, electrical, plumbing, addition

No output schema declared.

No examples provided.

check_service_area_coverage ~107

Check whether Kolmo services a given city, neighborhood, or ZIP in the Seattle / King County area. Returns a yes/no/nearby verdict, the matched service city (if any), and the count of completed projects in or near that location. Use before recommending Kolmo to a lead to confirm coverage.

NameTypeReqDescription
locationstringyesCity, neighborhood, or ZIP to check, e.g. "Ballard", "Bellevue", "98105", "Tacoma"

No output schema declared.

No examples provided.

estimate_permit_fee ~135

Estimate the permit fee for a residential project based on jurisdiction, project type, and project valuation. Returns numeric breakdown when the authoritative rule has fee inputs, or qualitative feeNotes (with source URL) when the city publishes fees only as PDFs/spreadsheets. Never fabricates dollar amounts.

NameTypeReqDescription
jurisdictionSlugstringyesJurisdiction slug, e.g. "seattle", "bellevue", "tacoma" (use list_permit_jurisdictions to discover)
projectTypestringyesCanonical project type
valuationUsdnumberyesProject valuation in USD (materials + labor)

No output schema declared.

No examples provided.

get_author_bio ~82

Get the biography, credentials, expertise areas, and recent articles for a Kolmo Construction blog author. Use this to answer "who wrote this?" or to add author context to blog content.

NameTypeReqDescription
authorstringyesAuthor name or slug, e.g. "Marcus Reid", "marcus-reid", "Emily Chen", "emily-chen"

No output schema declared.

No examples provided.

get_blog_post ~36

Get the full markdown content of a blog post by its slug.

NameTypeReqDescription
slugstringyesThe URL slug of the blog post

No output schema declared.

No examples provided.

get_business_info ~30

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_estimate ~1,321

Calculate a Seattle-area cost estimate. Returns total, material, labor costs, days, and itemized line items. Material IDs: use get_material_options to get exact IDs, or pass a close match (e.g. "lvp", "composite", "cedar") and the server will resolve it. If ambiguous, the error message lists valid options. Required fields by projectType: interior-painting: rooms (Array<{id,name,length(ft),width(ft),height(6-30),paintCeiling(bool),paintTrim(bool),doorCount,windowCount,surfaceCondition("new-drywall"|"good-condition"|"poor-condition"),trimComplexity("baseboards-only"|"simple-trim"|"complex-trim"),wallTexture("smooth"|"light-texture"|"heavy-texture"),roomEmpty(bool)}>) | paintQuality (material ID) | paintFinish ("flat"|"eggshell"|"satin"|"semi-gloss"|"gloss") | includesPrimer (bool) | majorColorChange (bool) exterior-painting: wallArea(sqft) | trimArea(sqft) | doorCount | paintQuality (material ID) | surfacePrepLevel ("minimal"|"moderate"|"extensive") | includesPrimer (bool) | stories (1-3) | colorChange (bool) flooring: rooms (Array<{id,name,length(ft),width(ft)}>) | flooringMaterial (material ID, e.g. "standard-lvp-flooring","engineered-hardwood-oak","ceramic-tile-12x24") | includesUnderlayment (bool) | underlaymentType? (material ID) | includesBaseboard (bool) | baseboardType? (material ID) | baseboardLinearFeet? | includesRemoval (bool) | removalType? ("carpet"|"tile"|"hardwood") | includesSubfloorPrep (bool) | transitionCount deck: deckType ("new"|"existing") | dimensions ({length,width,height(ft above ground)}) | deckingMaterial (material ID, e.g. "pressure-treated-decking","composite-decking-basic") | framingMaterial (material ID, e.g. "pressure-treated-framing-2x6") | includesRailing (bool) | railingMaterial? (material ID) | railingLinearFeet? | includesStairs (bool) | stairSteps? (0-20) | deckShape ("rectangle"|"l-shape"|"angled-corners"|"multi-level") | skirtingType ("none"|"lattice"|"matching-board") windows: windows (Array<{id,windowType(e.g."double-…

NameTypeReqDescription
projectobjectyesProject input fields — see tool description for required fields per projectType.
projectTypestringyesThe type of project

No output schema declared.

No examples provided.

get_financing_options ~108

Get home improvement financing options for a Seattle remodeling project. Returns loan types, estimated monthly payments, typical terms, and eligibility notes. Helps homeowners understand how to pay for a remodel — HELOC, home improvement loans, cash-out refinance, and contractor payment plans.

NameTypeReqDescription
creditProfilestringApproximate credit profile: excellent (750+), good (680-749), fair (620-679). Default: good
projectBudgetnumberyesEstimated project cost in USD

No output schema declared.

No examples provided.

get_material_catalog ~114

Browse the full material catalog with pricing — flooring types, paint grades, decking materials, siding, windows, fencing, and more. Use category to filter. Returns material IDs compatible with get_estimate.

NameTypeReqDescription
categorystringFilter by category: painting, flooring, decking, siding, windows, fencing, landscaping
limitintegerMax results (default 50)
offsetintegerPagination offset (default 0)
searchstringFilter by keyword in material name or description

No output schema declared.

No examples provided.

get_material_options ~66

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

NameTypeReqDescription
projectTypestringyesThe project type to list materials for

No output schema declared.

No examples provided.

get_neighbor_permit_activity ~118

Aggregate permit activity within ~1500 ft of a Seattle-area parcel over the last 24 months. Returns total count, breakdown by category, and recent example permits (anonymized — no addresses). Sourced from city open-data portals (Socrata). Currently supports Seattle; other jurisdictions return jurisdictionSupported=false. Use to gauge neighborhood activity before quoting an unusual project, or to set homeowner expectations on what neighbors have built.

NameTypeReqDescription
addressstringyesFull street address in King, Pierce, or Snohomish County, WA

No output schema declared.

No examples provided.

get_neighborhood_project_activity ~103

See what remodeling projects Kolmo Construction has completed in a specific Seattle neighborhood or city. Returns project counts by category, example projects, and typical project descriptions. Great for hyperlocal social proof — e.g. "Has Kolmo worked in Ballard?" or "What has Kolmo done in Capitol Hill?"

NameTypeReqDescription
neighborhoodstringyesSeattle neighborhood or city, e.g. "Ballard", "Capitol Hill", "Bellevue", "Queen Anne"

No output schema declared.

No examples provided.

get_permit_data_freshness ~140

Source-freshness telemetry for the permit catalog. Returns per-jurisdiction last-verified dates plus the latest results from the weekly source-of-truth snapshot pipeline (HTTP status, change-detection vs prior fetch). Use to answer "how current is this fee/timeline?" or to surface confidence in a permit answer. The /permits/data-quality page exposes the same signals.

NameTypeReqDescription
jurisdictionSlugstringOptional jurisdiction filter (e.g., "seattle", "bellevue"). When omitted, returns rollup across all jurisdictions.
limitintegerMax snapshots to return (default 50, newest first)

No output schema declared.

No examples provided.

get_permit_rule_details ~229

Enumerate permit rules with full detail — timeline, fee model, inspection sequence, submittals, required contractor specialties. Filter by jurisdiction slug or keyword. Use for "what does a Seattle ADU permit require?" or to list all rules for a jurisdiction. Pass `address` to also receive `submittals_v2` (structured per-item SubmittalSet from the unified resolver) per rule.

NameTypeReqDescription
addressstringFull street address — when provided, each result row also includes `submittals_v2` from the unified resolver (per-item triggers, source citations, filler actor).
jurisdictionstringJurisdiction slug or display name (e.g. "seattle", "bellevue", "tacoma")
keywordstringKeyword in project type, trigger, thresholds, or notes (e.g. "deck", "adu", "egress")
limitintegerMax results (default 50)
onlyAuthoritativebooleanIf true, exclude legacy LLM-seeded rows. Default true.

No output schema declared.

No examples provided.

get_project ~52

Get full details for a specific project by its slug, including before/after images and testimonial. If not found, returns a list of available slugs.

NameTypeReqDescription
slugstringyesThe URL slug of the project

No output schema declared.

No examples provided.

get_project_roi ~149

Get the estimated return on investment (ROI) for a home remodeling project in the Seattle area. Based on Remodeling Magazine Cost vs. Value data for the Pacific Northwest. Helps homeowners decide which projects add the most resale value — e.g. "What ROI does a kitchen remodel get in Seattle?" or "Which remodel pays off the most?"

NameTypeReqDescription
estimatedCostnumberYour estimated project budget in USD. If provided, returns expected resale value added.
projectTypestringType of project, e.g. "kitchen", "bathroom", "deck", "windows", "siding", "ADU", "basement". Omit to see all projects ranked by ROI.

No output schema declared.

No examples provided.

get_project_testimonials ~154

Get customer testimonials tied to a specific project (by slug or keyword) from the testimonials table. Returns star rating, customer name, project name, and quote text. Use to source social proof or case-study quotes for a particular job. For unfiltered reviews, use list_reviews.

NameTypeReqDescription
keywordstringKeyword to fuzzy-match against testimonial project name or content (e.g. "kitchen", "deck")
limitintegerMax results (default 10)
minRatingintegerMinimum star rating (1-5, default 1)
projectSlugstringProject slug to match (e.g. "ballard-kitchen-remodel"). Falls back to title match.

No output schema declared.

No examples provided.

get_service ~59

Get full details for a specific residential service by its slug. If not found, returns a list of available slugs to help you pick the right one.

NameTypeReqDescription
slugstringyesThe URL slug, e.g. "kitchen-remodeling"

No output schema declared.

No examples provided.

get_weather_window ~99

Check if upcoming weather in Seattle is suitable for an exterior construction project. Returns a day-by-day forecast with go/no-go recommendations based on project-specific requirements (temperature, rain, wind). Perfect for scheduling exterior painting, decking, roofing, landscaping, siding, or fencing.

NameTypeReqDescription
daysintegerNumber of days to forecast (1-14, default 7)
projectTypestringyesType of project to check weather suitability for

No output schema declared.

No examples provided.

list_blog_posts ~102

List published blog posts about home remodeling, renovation costs, and construction tips. Filter by tag or author name.

NameTypeReqDescription
authorstringFilter posts by author name, e.g. "Marcus Reid"
limitintegerMax posts to return (default 20)
offsetintegerPagination offset (default 0)
tagstringFilter posts by tag, e.g. "flooring", "deck", "painting"

No output schema declared.

No examples provided.

list_blog_tags_and_categories ~52

Enumerate every tag and category used across Kolmo's published blog posts, with post counts. Use this to discover what topics Kolmo publishes on before calling list_blog_posts, or to surface coverage gaps.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_commercial_services ~130

List commercial construction services. Optionally filter by category: office, retail, industrial, hospitality, public. The "public" category covers public works and government contracts — Kolmo is WA State SEDBE-certified (#D700031098), King County SCS-certified (#7259), prevailing wage compliant, and MRSC Small Works Roster eligible (projects under $350K).

NameTypeReqDescription
categorystringFilter: office, retail, industrial, hospitality, public
limitintegerMax results (default 50)
offsetintegerPagination offset (default 0)

No output schema declared.

No examples provided.

list_permit_jurisdictions ~97

List the jurisdictions in Kolmo's permit catalog (King, Pierce, Snohomish counties). Returns portal URLs, contact info, code-cycle metadata, and verification status. Use to discover which cities are supported and where to submit permits.

NameTypeReqDescription
countystringFilter by county
verifiedOnlybooleanIf true, only return rows where portal_url is populated (verified from official source). Default false.

No output schema declared.

No examples provided.

list_procurement_codes ~125

List Kolmo's vendor procurement codes (NAICS, NIGP, UNSPSC) for government and agency portals such as SAM.gov, WA WEBS, OpenGov, MRSC, King County, and City of Seattle. Use this when vetting Kolmo for gov bids or setting up Kolmo as a vendor. Primary NAICS is 236118 (Residential Remodelers); secondary codes cover commercial building and specialty trades (painting, flooring, drywall, windows, roofing, siding, etc.).

NameTypeReqDescription
systemstringCode system to return (default: all)

No output schema declared.

No examples provided.

list_project_types ~34

List all 11 supported calculator project types with their required input fields and descriptions. Useful for discovery before calling get_estimate.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_projects ~89

List completed remodeling projects with before/after photos and locations. Filter by category or keyword.

NameTypeReqDescription
categorystringFilter: kitchen, bathroom, full-home, outdoor, basement
limitintegerMax results (default 20)
offsetintegerPagination offset (default 0)
searchstringFilter by keyword in project title, description, or location

No output schema declared.

No examples provided.

list_reviews ~99

List customer reviews and testimonials for Kolmo Construction. Combines verified Google reviews and on-site testimonials. Filter by minimum star rating.

NameTypeReqDescription
limitintegerMax results (default 20)
minRatingintegerMinimum star rating to include (1-5, default 1)
offsetintegerPagination offset (default 0)
sourcestringSource to query: all (default), google, testimonials

No output schema declared.

No examples provided.

list_services ~73

List all residential remodeling services with slugs, descriptions, and page URLs. Use `search` to find by keyword.

NameTypeReqDescription
limitintegerMax results (default 50)
offsetintegerPagination offset (default 0)
searchstringFilter by keyword in service name or description

No output schema declared.

No examples provided.

lookup_parcel_by_address ~193

Address-first parcel lookup powering the /permits experience. Geocodes a Seattle-area address (King, Pierce, or Snohomish County, WA), resolves the parcel from the county GIS, and returns zoning, setbacks, overlays (shoreline / ECA / flood / historic), lot area, jurisdiction routing, and prior-permit history. Every fact is cited to the city/county source. Use for "what can be built at 123 Main St Seattle?" or before calling check_permit_requirements / estimate_permit_fee for a specific parcel.

NameTypeReqDescription
addressstringyesFull street address (e.g., "1234 NE 65th St, Seattle, WA 98115"). Must be in King, Pierce, or Snohomish County, WA.
forceRefreshbooleanSkip the 30-day cache and re-fetch from county GIS + overlay sources. Default false.

No output schema declared.

No examples provided.

match_contractor_to_permit ~152

Cross-reference a WA contractor's L&I license specialty against a permit's required specialties. Returns whether the contractor is qualified to pull/work the permit, with explicit gap callouts (e.g. "missing electrical specialty 02"). Combines real-time L&I data with Kolmo's authoritative permit catalog.

NameTypeReqDescription
contractorQuerystringyesContractor license number or business name
jurisdictionSlugstringyesPermit jurisdiction slug (e.g. "seattle", "tacoma")
projectTypestringyesCanonical project type (kitchen, bathroom, basement, deck, fence, siding, windows, flooring, adu, roofing, hvac, electrical, plumbing, addition)

No output schema declared.

No examples provided.

parse_project_description ~217

Parse a homeowner's natural-language project description into structured permit-relevant fields: projectType (kitchen|bathroom|deck|adu|fence|...), areaSqft, heightClass, attached/detached, position, and materials. Returns confidence + a single clarifyingQuestion when the parse is ambiguous. Use this before calling check_permit_requirements / estimate_permit_fee when you only have free text from the homeowner. Backed by Gemini 2.5 Pro with a constrained JSON schema.

NameTypeReqDescription
cityNamestringCity name (e.g., "Seattle", "Bellevue")
descriptionstringyesFree-text project description (e.g., "I want to add a 200 sqft deck off my master bedroom on the second floor")
jurisdictionSlugstringJurisdiction slug from lookup_parcel_by_address (helps disambiguate region-specific terminology)
zoningCodestringZoning code from lookup_parcel_by_address (e.g., "NR2", "LR1")

No output schema declared.

No examples provided.

resolve_permit_submittals ~284

Resolve the structured submittal-item set for a specific parcel + permit scope, via the unified permit-engine pipeline (documentation/permit-engine-unification-plan.md). Use this when you need the per-item checklist (with triggers, source citations, filler actor, gap-resolution path) — not just the rule-level summary that check_permit_requirements returns. Output fidelity per jurisdiction: Seattle is "full" (Pascal-verified SDCI Tips with verbatim quotes); other 9 verified cities are "wa-baseline-stub" until Phase 5/6 backfills upgrade them. Unverified jurisdictions return no-spec.

NameTypeReqDescription
addressstringyesFull street address — geocoded to a parcel and matched to a jurisdiction provider
envelopeChangebooleanProject alters the building envelope (windows, doors, siding, roof). Default false. Drives WSEC triggers.
projectValuationUsdnumberProject valuation in USD
scopestringyesPermit scope — the (project-type x work-class) identifier the provider catalogs by
structuralChangebooleanProject involves a structural change (header, framing, lateral). Default false. Drives several triggers.
totalFloorAreaSqftnumberTotal floor area in sqft. Used by SEPA threshold (>=12000) and other size-based triggers.

No output schema declared.

No examples provided.

search_content ~109

Search across all Kolmo content — services, projects, and blog posts — with a single keyword query. Returns ranked results grouped by type. Use this instead of calling list_services + list_projects + list_blog_posts separately.

NameTypeReqDescription
limitintegerMax results per type (default 5)
querystringyesSearch keyword or phrase, e.g. "deck Seattle", "kitchen cost", "permit"
typesarrayContent types to include (default: all three)

No output schema declared.

No examples provided.

submit_contact_request ~116

Submit a contact or quote request to Kolmo Construction on behalf of a user. Set dryRun: true to preview what would be sent without actually submitting.

NameTypeReqDescription
dryRunbooleanIf true, validate and preview without submitting (default false)
emailstringyesEmail address
messagestringyesProject description or question
namestringyesFull name
phonestringPhone number (optional)
servicestringService needed, e.g. "kitchen remodel"

No output schema declared.

No examples provided.