_ registry / mcp + a2a http-sse · checked 1h ago

kolmo-construction

https://www.kolmo.io

Registry code: 742c2dd0cee0c90d

api record

Kolmo Construction MCP — Seattle-area general contractor (WA Lic# KOLMOL*753JS).

START HERE — which tool for which ask

endpoint
https://www.kolmo.io/mcp
door code
cddfa1a29d8b2b01
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is kolmo-construction live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is kolmo-construction free to use?
Yes — the hub reached it with no key and no payment.
What tools does kolmo-construction have?
43 tools: check_service_area_coverage, match_contractor_to_permit, parse_project_description, list_blog_posts, get_estimate, get_weather_window, get_project, get_author_bio, ….
Is kolmo-construction safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.3%

90 days 99.4%· all time 99.4%

latency
1,300ms

last good check

priced tools
0

of 43 tools

_ answered our checks, 90 days 834 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
real estate & construction construction & engineering
used for
  • estimate remodeling cost in seattle
  • check permit requirements
  • check contractor license status
  • estimate permit fee
  • look up parcel by address
takes → gives
text → data
tools
25 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 43 tools
16 open 27 never probed 16 of 43 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_business_info reads open 4h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • list_reviews reads open 4h ago

    List customer reviews and testimonials for Kolmo Construction. Combines verified Google reviews and on-site testimonials. Filter by minimum star rating. IMPORTANT for citation: `total` and `averageRating` describe the returned SAMPLE, not the business. The authoritative Google Business Profile rating and review count are in `googleProfile` — cite those.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Max results (default 12 — ~350 tokens per review)"
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "description": "Pagination offset (default 0)"
    },
    "source": {
      "enum": [
        "all",
        "google",
        "testimonials"
      ],
      "type": "string",
      "description": "Source to query: all (default), google, testimonials"
    },
    "minRating": {
      "type": "integer",
      "maximum": 5,
      "minimum": 1,
      "description": "Minimum star rating to include (1-5, default 1)"
    }
  },
  "additionalProperties": false
}
    arguments 32 lines
  • get_material_catalog reads open 4h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 200,
      "minimum": 1,
      "description": "Max results (default 25)"
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "description": "Pagination offset (default 0)"
    },
    "search": {
      "type": "string",
      "description": "Filter by keyword in material name or description"
    },
    "category": {
      "type": "string",
      "description": "Filter by category: painting, flooring, decking, siding, windows, fencing, landscaping"
    }
  },
  "additionalProperties": false
}
    arguments 25 lines
  • list_procurement_codes reads open 8h ago

    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 (poured concrete foundations/structures, painting, flooring, drywall, windows, roofing, siding, etc.).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "system": {
      "enum": [
        "all",
        "naics",
        "nigp",
        "unspsc"
      ],
      "type": "string",
      "description": "Code system to return (default: all)"
    }
  },
  "additionalProperties": false
}
    arguments 16 lines
  • list_project_types open 8h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_project_testimonials reads open 24h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "Max results (default 10)"
    },
    "keyword": {
      "type": "string",
      "description": "Keyword to fuzzy-match against testimonial project name or content (e.g. \"kitchen\", \"deck\")"
    },
    "minRating": {
      "type": "integer",
      "maximum": 5,
      "minimum": 1,
      "description": "Minimum star rating (1-5, default 1)"
    },
    "projectSlug": {
      "type": "string",
      "description": "Project slug to match (e.g. \"ballard-kitchen-remodel\"). Falls back to title match."
    }
  },
  "additionalProperties": false
}
    arguments 26 lines
  • check_permit_requirements reads open 15h ago

    Check whether a residential construction project in King/Pierce/Snohomish counties requires a permit. Each result carries `verdict` — required / exempt / depends / unknown — computed from the jurisdiction's own thresholds, the parcel's overlays (when `address` is given) and the `facts` you pass; when it is `depends`, `verdict.questions` names the facts to ask the homeowner and pass back. `requiresPermit` is the rule's default posture, not the answer. Also returns timeline, fees, inspections, submittals and the official source URL. Use for "Do I need a permit to build a deck in Seattle?". Pass `address` to also get the per-item submittal set (`submittals_v2`). Kinds of work that are not project types (a shed, a retaining wall, a pool, an antenna, grading) are answered from the jurisdiction's own rule for that work when `location` or `address` names one; `verdict.separatePermits` lists any other permit the same work needs (shoreline, floodplain, grading).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "facts": {
      "type": "object",
      "description": "What the homeowner has said about the scope, keyed by fact. Each result carries `verdict.questions` naming the facts still open, with their keys; pass the answers back here. Parcel facts (inCriticalArea, inFloodZone, inShoreline, historicOrLandmark, and those a city maps itself, such as inSingleFamilyResidentialZone in Issaquah) are read from the parcel when `address` is given; pass them only without an address.",
      "additionalProperties": {
        "type": [
          "number",
          "boolean"
        ]
      }
    },
    "limit": {
      "type": "integer",
      "maximum": 200,
      "minimum": 1,
      "description": "Max matching rules to return (default 25). Narrow with projectType/location before raising it."
    },
    "address": {
      "type": "string",
      "description": "Full 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."
    },
    "location": {
      "type": "string",
      "description": "City or jurisdiction slug, e.g. \"Seattle\", \"Bellevue\", \"Tacoma\", \"king-county-unincorporated\""
    },
    "projectType": {
      "type": "string",
      "description": "Project type — canonical: kitchen, bathroom, basement, deck, fence, siding, windows, flooring, adu, roofing, hvac, electrical, plumbing, addition. Also a kind of work, answered with a location or address: accessory-structure (shed), retaining-wall, paving (driveway, patio), swimming-pool, interior-alteration, garage-conversion, awning, play-structure, antenna, water-tank, underground-tank, grading, street-tree"
    },
    "guardRunLengthFt": {
      "type": "number",
      "description": "Total guard/railing run in the scope of work, feet. A guard is separately permittable from the surface it stands on; a deck exemption does not carry it."
    },
    "deckOverStoryBelow": {
      "type": "boolean",
      "description": "True if any part of the deck is over a basement or a story below. A deck under 30 in is still NOT exempt in Kirkland if it sits over a story."
    },
    "deckOnAccessibleRoute": {
      "type": "boolean",
      "description": "True if the deck is part of an accessible route to a building entrance — an independent permit trigger, separate from height."
    },
    "deckHeightAboveGradeIn": {
      "type": "number",
      "description": "Deck walking surface above grade, inches — measured to the grade below at any point within 36 in of the outer edge."
    }
  },
  "additionalProperties": false
}
    arguments 50 lines
  • list_permit_jurisdictions reads open 15h ago

    List the jurisdictions in Kolmo's permit catalog (King, Pierce, Snohomish counties). Compact by default — `results` is keyed by county (King / Pierce / Snohomish), each a list of {slug, name, verified} — the whole catalogue in one call (~4K tokens), enough to pick a jurisdictionSlug for estimate_permit_fee, check_permit_requirements or get_permit_rule_details. Pass `slug` for one jurisdiction's full record (department, fee-schedule URL, phone, code cycles, notes), or `detail: true` for full records on every row.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "description": "One jurisdiction by slug, e.g. \"bellevue\" or \"mercer-island\". Returns its full record."
    },
    "county": {
      "enum": [
        "King",
        "Pierce",
        "Snohomish"
      ],
      "type": "string",
      "description": "Filter by county"
    },
    "detail": {
      "type": "boolean",
      "description": "If true, every row carries the full record. Default false (compact rows). The full catalogue in detail is ~9x larger — prefer `slug` when you need one city."
    },
    "verifiedOnly": {
      "type": "boolean",
      "description": "If true, only return rows where portal_url is populated (verified from official source). Default false."
    }
  },
  "additionalProperties": false
}
    arguments 27 lines
  • list_commercial_services reads open 15h ago

    List commercial construction services with slugs and citable page URLs. 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). Pass a `slug` for one service's full write-up.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "description": "One service, with its full description"
    },
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Max results (default 50)"
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "description": "Pagination offset (default 0)"
    },
    "category": {
      "type": "string",
      "description": "Filter: office, retail, industrial, hospitality, public"
    }
  },
  "additionalProperties": false
}
    arguments 25 lines
  • get_common_plan_review_corrections open 1h ago

    Corrections Seattle plan reviewers most often send on ADU permits, from the City's public correction letters: share of permits per category and the code cited. Shares are of permits that went to correction.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "zone": {
      "type": "string",
      "maxLength": 40,
      "description": "e.g. NR, LR1"
    },
    "limit": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1
    },
    "subtype": {
      "enum": [
        "adu-detached",
        "adu-attached"
      ],
      "type": "string",
      "default": "adu-detached"
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • get_permit_data_freshness reads open 1h ago

    Source-freshness telemetry for the permit catalog. Returns per-jurisdiction last-verified dates, a per-jurisdiction source-health rollup (which cities have a reachable / gone / blocked official source right now), and the latest results from the weekly source-of-truth snapshot pipeline (HTTP status, change-detection vs prior fetch). Failures are classified: `missing` means the page is gone, `blocked` means the host refused our fetch and is NOT evidence the source is gone. 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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 200,
      "minimum": 1,
      "description": "Max snapshots to return (default 5, newest first)"
    },
    "jurisdictionSlug": {
      "type": "string",
      "description": "Optional jurisdiction filter (e.g., \"seattle\", \"bellevue\"). When omitted, returns rollup across all jurisdictions."
    }
  },
  "additionalProperties": false
}
    arguments 16 lines
  • get_permit_rule_details reads open 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 200,
      "minimum": 1,
      "description": "Max results (default 10 — rules are ~1K tokens each)"
    },
    "address": {
      "type": "string",
      "description": "Full street address — when provided, each result row also includes `submittals_v2` from the unified resolver (per-item triggers, source citations, filler actor)."
    },
    "keyword": {
      "type": "string",
      "description": "Keyword in project type, trigger, thresholds, or notes (e.g. \"deck\", \"adu\", \"egress\")"
    },
    "jurisdiction": {
      "type": "string",
      "description": "Jurisdiction slug or display name (e.g. \"seattle\", \"bellevue\", \"tacoma\")"
    },
    "onlyAuthoritative": {
      "type": "boolean",
      "description": "Default true: return only 'authoritative' and 'wa-baseline' rules, the two tiers Kolmo's city pages show. Kept for compatibility: no other tier is held, so false returns the same rules."
    }
  },
  "additionalProperties": false
}
    arguments 28 lines
  • list_projects reads open 8h ago

    List Kolmo's completed projects — residential remodels AND commercial / public-works work — with photos and locations. Filter by category or keyword; get_project has the full case study. Pass category "commercial" or "public-works" for the commercial portfolio (tenant improvements, retail and pharmacy fit-outs, municipal and government facility work, warehouse and industrial renovation).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Max results (default 10)"
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "description": "Pagination offset (default 0)"
    },
    "search": {
      "type": "string",
      "description": "Filter by keyword in project title, description, or location"
    },
    "category": {
      "type": "string",
      "description": "Filter. Residential: kitchen, bathroom, full-home, outdoor, garage, basement. Commercial: commercial, public-works."
    }
  },
  "additionalProperties": false
}
    arguments 25 lines
  • list_services open 29h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Max results (default 50)"
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "description": "Pagination offset (default 0)"
    },
    "search": {
      "type": "string",
      "description": "Filter by keyword in service name or description"
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
  • get_project_roi reads open 24h ago

    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?"

    mcp-tool

    {
  "type": "object",
  "properties": {
    "projectType": {
      "type": "string",
      "description": "Type of project, e.g. \"kitchen\", \"bathroom\", \"deck\", \"windows\", \"siding\", \"ADU\", \"basement\". Omit to see all projects ranked by ROI."
    },
    "estimatedCost": {
      "type": "number",
      "description": "Your estimated project budget in USD. If provided, returns expected resale value added."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • list_blog_tags_and_categories open 24h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • check_service_area_coverage unknown 38h ago

    Check whether Kolmo takes work in a given city, neighborhood, ZIP or address. Kolmo works across Washington: Puget Sound (Bellingham to Olympia) is the core area and the rest of the state is case by case. coverage is primary (a featured city or Seattle neighborhood), nearby (in the core area), case_by_case (Washington, outside Puget Sound), unconfirmed (not a place this check recognizes: treat it as in area) or out_of_area (outside Washington, the ONLY value that means Kolmo does not take the work). Follow `guidance`. Also returns the count of completed projects in or near that location.

    mcp-tool

    {
  "type": "object",
  "required": [
    "location"
  ],
  "properties": {
    "location": {
      "type": "string",
      "description": "City, neighborhood, ZIP or address to check, e.g. \"Ballard\", \"Normandy Park\", \"98105\", \"Tacoma\""
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • match_contractor_to_permit reads unknown 12h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "contractorQuery",
    "jurisdictionSlug",
    "projectType"
  ],
  "properties": {
    "projectType": {
      "type": "string",
      "description": "Canonical project type (kitchen, bathroom, basement, deck, fence, siding, windows, flooring, adu, roofing, hvac, electrical, plumbing, addition)"
    },
    "contractorQuery": {
      "type": "string",
      "description": "Contractor license number, business name, UBI or phone number"
    },
    "jurisdictionSlug": {
      "type": "string",
      "description": "Permit jurisdiction slug (e.g. \"seattle\", \"tacoma\")"
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • parse_project_description unknown 12h ago

    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 an LLM with a constrained JSON schema.

    mcp-tool

    {
  "type": "object",
  "required": [
    "description"
  ],
  "properties": {
    "cityName": {
      "type": "string",
      "description": "City name (e.g., \"Seattle\", \"Bellevue\")"
    },
    "zoningCode": {
      "type": "string",
      "description": "Zoning code from lookup_parcel_by_address (e.g., \"NR2\", \"LR1\")"
    },
    "description": {
      "type": "string",
      "maxLength": 2000,
      "minLength": 1,
      "description": "Free-text project description (e.g., \"I want to add a 200 sqft deck off my master bedroom on the second floor\")"
    },
    "jurisdictionSlug": {
      "type": "string",
      "description": "Jurisdiction slug from lookup_parcel_by_address (helps disambiguate region-specific terminology)"
    }
  },
  "additionalProperties": false
}
    arguments 27 lines
  • list_blog_posts reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "tag": {
      "type": "string",
      "description": "Filter posts by tag, e.g. \"flooring\", \"deck\", \"painting\""
    },
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "Max posts to return (default 10)"
    },
    "author": {
      "type": "string",
      "description": "Filter posts by author name, e.g. \"Marcus Reid\""
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "description": "Pagination offset (default 0)"
    }
  },
  "additionalProperties": false
}
    arguments 25 lines
  • get_estimate reads unknown 31h ago

    Seattle cost estimate: range, material/labor split, days, line items. Fields per type below; their allowed values, ranges and pricing rules are in list_project_types. ?=optional; (mat)=get_material_options ID (a unique close name also resolves; an ambiguous one lists candidates). interior-painting: rooms([{id,name,length,width,height,paintCeiling,paintTrim,doorCount,windowCount,surfaceCondition,trimComplexity,wallTexture,roomEmpty}]); paintQuality(mat); includesPrimer; majorColorChange?(+colorChange{currentColor,targetColor}) exterior-painting: wallArea,trimArea; doorCount; paintQuality(mat); surfacePrepLevel; includesPrimer; stories?; colorChange?(+colorChangeData{currentColor,targetColor}) flooring: rooms([{id,name,length,width}]); flooringMaterial(mat); includesUnderlayment,includesBaseboard,includesRemoval,includesSubfloorPrep; underlaymentType?,baseboardType?(mat); baseboardLinearFeet?; removalType?; transitionCount? deck: deckType; dimensions({length,width≤200,height≤30 ft}); deckingMaterial(mat); framingMaterial(mat); includesRailing,includesStairs; railingMaterial?,finishType?(mat); railingLinearFeet?; stairSteps?; landingRequired?; deckShape?; skirtingType?; existingDeckWorkItems? windows: windows([{id,windowType,width,height,quantity}]); qualityLevel; includesTrimWork,includesRemoval,energyEfficient; trimMaterial?(mat) siding: wallArea; sidingMaterial(mat); homeHeight; includesInsulation,includesRemoval,soffit; insulationType?(mat); existingSidingType?; trimLinearFeet; soffitLinearFeet? fence: linearFeet; fenceMaterial(mat); height; gateCount; gateWidth?; style?; terrain; includesRemoval,concreteFootings landscaping: yardArea; includesIrrigation,includesSod,includesMulch,includesSitePrep; irrigationType?; irrigationZones?; sodSquareFeet?; mulchSquareFeet?; plants?([{id,plantType,quantity,size}]); hardscapeFeatures?([{id,featureType,squareFeet,material}]) kitchen: kitchenSize; scope; cabinets; countertop; appliances; flooring; backsplash?,plumbingRelocation?,electricalUpgrade?,island?,lighting?; wallRemoval?; gasLine?,rangeHood? bathroom: bathroomType; bathroomSize; scope; showerTub; vanity; tileWork; showerWalls?; heatedFloors?,newLighting?,ventilation?,plumbingRelocation?,glassDoor?,showerSeat?,handShower?; grabBars? basement: basementSize; scope; ceilingHeight; moistureCondition; egress; bathroom; kitchenette; bedroomCount?; flooring; insulation; hvac; electricalSubpanel?,homeAgePre1978? adu: type; sizeSqft; finishTier; dadu only: foundation?,sitework?,utilityRunFeet?,preApprovedPlan?; treeRemovalCount?; homeAgePre1978? ada: projectScope; modifications({grabBars,walkInShower,widerDoorways,ramp,nonSlipFlooring,leverHandles,raisedToilet,rollUnderSink,accessibleCounters,stairLift}, ≥1 true); currentCondition; homeStories?; doorwayCount?; rampLengthFeet?; flooringSquareFeet? electrical: items[{id,quantity}] (ids: get_material_options) plumbing: items[{id,quantity}] (ids: get_material_options) garage-doors: items[{id,quantity}] (ids: get_material_options) doors: items[{id,quantity}] (ids: get_material_options) concrete: items[{id,quantity}] (ids: get_material_options) insulation: items[{id,quantity}] (ids: get_material_options) gutters: items[{id,quantity}] (ids: get_material_options)

    mcp-tool

    {
  "type": "object",
  "required": [
    "projectType",
    "project"
  ],
  "properties": {
    "project": {
      "type": "object",
      "description": "Project input fields — named per projectType in the tool description; allowed values in list_project_types.",
      "additionalProperties": {}
    },
    "projectType": {
      "enum": [
        "interior-painting",
        "exterior-painting",
        "flooring",
        "deck",
        "windows",
        "siding",
        "fence",
        "landscaping",
        "kitchen",
        "bathroom",
        "basement",
        "adu",
        "ada",
        "electrical",
        "plumbing",
        "garage-doors",
        "doors",
        "concrete",
        "insulation",
        "gutters"
      ],
      "type": "string",
      "description": "The type of project"
    }
  },
  "additionalProperties": false
}
    arguments 41 lines
  • get_weather_window reads unknown 17h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "projectType"
  ],
  "properties": {
    "days": {
      "type": "integer",
      "maximum": 14,
      "minimum": 1,
      "description": "Number of days to forecast (1-14, default 7)"
    },
    "projectType": {
      "enum": [
        "exterior-painting",
        "deck",
        "roofing",
        "landscaping",
        "siding",
        "fence",
        "windows",
        "interior"
      ],
      "type": "string",
      "description": "Type of project to check weather suitability for"
    }
  },
  "additionalProperties": false
}
    arguments 29 lines
  • get_project unknown 17h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "The URL slug of the project"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • get_author_bio reads unknown 31h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "author"
  ],
  "properties": {
    "author": {
      "type": "string",
      "description": "Author name or slug, e.g. \"Marcus Reid\", \"marcus-reid\", \"Emily Chen\", \"emily-chen\""
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • check_contractor_license_status reads unknown 12h ago

    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. Search by license number, business name, UBI, or phone number. Results are ranked closest match first; when `identified` is false, several businesses match and none should be reported as the contractor.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "Contractor license number (e.g. \"KOLMOL*753JS\"), business name (e.g. \"Kolmo LLC\"), 9-digit UBI, or phone number"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • estimate_permit_fee reads unknown 31h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "jurisdictionSlug",
    "projectType",
    "valuationUsd"
  ],
  "properties": {
    "zone": {
      "type": "string",
      "description": "The lot's zoning code, e.g. \"R-20\". Needed where the fee table has a column per zone (hunts-point: R-20/R-20A or R-40)."
    },
    "areaSqft": {
      "type": "number",
      "description": "Square feet of the work. Needed where the jurisdiction charges per square foot instead of on valuation (king-county-unincorporated: deck, addition, basement conversion, ADU), or off a table by floor area (hunts-point: kitchen, bathroom, basement, addition, ADU).",
      "exclusiveMinimum": 0
    },
    "projectType": {
      "enum": [
        "kitchen",
        "bathroom",
        "basement",
        "deck",
        "fence",
        "siding",
        "windows",
        "flooring",
        "adu",
        "roofing",
        "hvac",
        "electrical",
        "plumbing",
        "addition"
      ],
      "type": "string",
      "description": "Canonical project type"
    },
    "valuationUsd": {
      "type": "number",
      "minimum": 0,
      "description": "Project valuation in USD (materials + labor)"
    },
    "jurisdictionSlug": {
      "type": "string",
      "description": "Jurisdiction slug, e.g. \"seattle\", \"bellevue\", \"tacoma\" (use list_permit_jurisdictions to discover)"
    }
  },
  "additionalProperties": false
}
    arguments 49 lines
  • get_payment_link unknown never probed

    Invoices for an accepted Kolmo quote, with amount, status and the kolmo.io quote page where the person pays them. Never collect card or bank details.

    mcp-tool

    {
  "type": "object",
  "required": [
    "quoteLink"
  ],
  "properties": {
    "quoteLink": {
      "type": "string",
      "maxLength": 300,
      "minLength": 36,
      "description": "The person's kolmo.io/quotes/<id> link, as Kolmo sent it. Never guess one."
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • get_permit_timeline unknown 38h ago

    Measured days from application to issue (median and 80th percentile), City vs applicant days, and review cycles, from the city's issued-permit records. A city not yet covered returns the covered list; groups under 30 permits are not reported.

    mcp-tool

    {
  "type": "object",
  "required": [
    "projectType"
  ],
  "properties": {
    "subtype": {
      "enum": [
        "adu-detached",
        "adu-attached",
        "adu-detached-preapproved",
        "adu-garage-conversion"
      ],
      "type": "string"
    },
    "projectType": {
      "enum": [
        "adu",
        "addition",
        "deck",
        "basement",
        "alteration",
        "new-home",
        "new-multifamily"
      ],
      "type": "string",
      "description": "new-multifamily: townhouses and other middle-housing units built as a set"
    },
    "valuationUsd": {
      "type": "number",
      "exclusiveMinimum": 0
    },
    "jurisdictionSlug": {
      "type": "string",
      "default": "seattle"
    }
  },
  "additionalProperties": false
}
    arguments 39 lines
  • search_content reads unknown 38h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1,
      "description": "Max results per type (default 5)"
    },
    "query": {
      "type": "string",
      "minLength": 1,
      "description": "Search keyword or phrase, e.g. \"deck Seattle\", \"kitchen cost\", \"permit\""
    },
    "types": {
      "type": "array",
      "items": {
        "enum": [
          "services",
          "projects",
          "blog"
        ],
        "type": "string"
      },
      "description": "Content types to include (default: all three)"
    }
  },
  "additionalProperties": false
}
    arguments 32 lines
  • get_blog_post unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "The URL slug of the blog post"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • answer_permit_question reads unknown 20h ago

    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?"

    mcp-tool

    {
  "type": "object",
  "required": [
    "address",
    "question"
  ],
  "properties": {
    "address": {
      "type": "string",
      "maxLength": 250,
      "minLength": 3,
      "description": "Full street address in King, Pierce, or Snohomish County, WA"
    },
    "question": {
      "type": "string",
      "maxLength": 1000,
      "minLength": 3,
      "description": "A single permit/zoning/setback/overlay question about this parcel"
    }
  },
  "additionalProperties": false
}
    arguments 22 lines
  • get_neighborhood_project_activity unknown 20h ago

    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?"

    mcp-tool

    {
  "type": "object",
  "required": [
    "neighborhood"
  ],
  "properties": {
    "neighborhood": {
      "type": "string",
      "description": "Seattle neighborhood or city, e.g. \"Ballard\", \"Capitol Hill\", \"Bellevue\", \"Queen Anne\""
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • get_neighbor_permit_activity reads unknown 20h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "maxLength": 250,
      "minLength": 3,
      "description": "Full street address in King, Pierce, or Snohomish County, WA"
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • get_service unknown 29h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "The URL slug, e.g. \"kitchen-remodeling\""
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • get_financing_options unknown 22h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "projectBudget"
  ],
  "properties": {
    "creditProfile": {
      "enum": [
        "excellent",
        "good",
        "fair"
      ],
      "type": "string",
      "description": "Approximate credit profile: excellent (750+), good (680-749), fair (620-679). Default: good"
    },
    "projectBudget": {
      "type": "number",
      "minimum": 1000,
      "description": "Estimated project cost in USD"
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • get_material_options reads unknown 22h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "projectType"
  ],
  "properties": {
    "projectType": {
      "enum": [
        "interior-painting",
        "exterior-painting",
        "flooring",
        "deck",
        "windows",
        "siding",
        "fence",
        "landscaping",
        "kitchen",
        "bathroom",
        "basement",
        "adu",
        "ada",
        "electrical",
        "plumbing",
        "garage-doors",
        "doors",
        "concrete",
        "insulation",
        "gutters"
      ],
      "type": "string",
      "description": "The project type to list materials for"
    }
  },
  "additionalProperties": false
}
    arguments 35 lines
  • submit_contact_request unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name",
    "email",
    "message"
  ],
  "properties": {
    "name": {
      "type": "string",
      "minLength": 1,
      "description": "Full name"
    },
    "email": {
      "type": "string",
      "format": "email",
      "description": "Email address"
    },
    "phone": {
      "type": "string",
      "description": "Phone number (optional)"
    },
    "dryRun": {
      "type": "boolean",
      "description": "If true, validate and preview without submitting (default false)"
    },
    "message": {
      "type": "string",
      "minLength": 10,
      "description": "Project description or question"
    },
    "service": {
      "type": "string",
      "description": "Service needed, e.g. \"kitchen remodel\""
    }
  },
  "additionalProperties": false
}
    arguments 38 lines
  • resolve_permit_submittals reads unknown never probed

    Resolve the structured submittal-item set for a specific parcel + permit scope, via the unified permit-engine pipeline. 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. Each set states its `fidelity`, which varies by city and scope: "full" (every item cites the code section, tip or City page it rests on), "min-viable", or "wa-baseline-stub". Unverified jurisdictions return no-spec.

    mcp-tool

    {
  "type": "object",
  "required": [
    "address",
    "scope"
  ],
  "properties": {
    "scope": {
      "enum": [
        "addition-alteration",
        "adu-aadu",
        "adu-dadu",
        "adu-dadu-standard-plan",
        "deck",
        "demo-housing",
        "garage",
        "shed",
        "reroof",
        "fence",
        "retaining-wall",
        "kitchen-remodel",
        "bathroom-remodel",
        "window-replacement",
        "siding",
        "mechanical",
        "sf-new-construction",
        "tu-new-construction"
      ],
      "type": "string",
      "description": "Permit scope — the (project-type x work-class) identifier the provider catalogs by"
    },
    "address": {
      "type": "string",
      "maxLength": 250,
      "minLength": 3,
      "description": "Full street address — geocoded to a parcel and matched to a jurisdiction provider"
    },
    "envelopeChange": {
      "type": "boolean",
      "description": "Project alters the building envelope (windows, doors, siding, roof). Default false. Drives WSEC triggers."
    },
    "structuralChange": {
      "type": "boolean",
      "description": "Project involves a structural change (header, framing, lateral). Default false. Drives several triggers."
    },
    "totalFloorAreaSqft": {
      "type": "number",
      "description": "Total floor area in sqft. Used by SEPA threshold (>=12000) and other size-based triggers."
    },
    "projectValuationUsd": {
      "type": "number",
      "description": "Project valuation in USD"
    }
  },
  "additionalProperties": false
}
    arguments 56 lines
  • lookup_parcel_by_address reads unknown never probed

    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. Zoning, setbacks and building facts carry the city/county source they came from (geocode, lot geometry and assessor records do not). An overlay with offLotFt was mapped that many feet beside the lot, not on it; screen: true marks a county map read inside a city, or a city map its own code calls only a guide, a reason to ask, not the city's designation. Use for "what can be built at 123 Main St Seattle?" or before calling check_permit_requirements / estimate_permit_fee for a specific parcel.

    mcp-tool

    {
  "type": "object",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "maxLength": 250,
      "minLength": 3,
      "description": "Full street address (e.g., \"1234 NE 65th St, Seattle, WA 98115\"). Must be in King, Pierce, or Snohomish County, WA."
    },
    "forceRefresh": {
      "type": "boolean",
      "description": "Skip the 30-day cache and re-fetch from county GIS + overlay sources. Default false."
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • find_rebates unknown 22h ago

    Seattle-area energy rebates (PSE, Seattle City Light, Seattle Clean Heat, HomeWise, WA HEAR) for a job: what each pays, who must install it, the price after rebates, and the program page with the date Kolmo read it. An address fills in utility, city and year built. A "check" line names the fact it still needs.

    mcp-tool

    {
  "type": "object",
  "required": [
    "work"
  ],
  "properties": {
    "city": {
      "type": "string",
      "maxLength": 60,
      "description": "When there is no address."
    },
    "work": {
      "type": "array",
      "items": {
        "enum": [
          "heat-pump",
          "heat-pump-water-heater",
          "attic-insulation",
          "wall-insulation",
          "floor-insulation",
          "air-sealing",
          "duct-sealing",
          "ventilation-fan",
          "windows",
          "smart-thermostat",
          "energy-assessment",
          "induction-cooking",
          "electric-panel"
        ],
        "type": "string"
      },
      "maxItems": 6,
      "minItems": 1
    },
    "address": {
      "type": "string",
      "maxLength": 250
    },
    "heating": {
      "enum": [
        "electric-zonal",
        "electric-furnace",
        "heat-pump",
        "gas",
        "oil",
        "propane"
      ],
      "type": "string",
      "description": "Main heat today; electric-zonal = baseboard/wall."
    },
    "quantity": {
      "type": "number",
      "description": "Windows: count. Insulation: sq ft."
    },
    "confirmed": {
      "type": "array",
      "items": {
        "enum": [
          "old-windows-wood-or-metal",
          "attic-0-4-inches",
          "walls-empty",
          "floor-0-4-inches"
        ],
        "type": "string"
      },
      "description": "Ids from a line's confirmable list the person said are true."
    },
    "yearBuilt": {
      "type": "integer"
    },
    "annualIncome": {
      "type": "number"
    },
    "householdSize": {
      "type": "integer"
    },
    "projectCostUsd": {
      "type": "number"
    },
    "electricUtility": {
      "enum": [
        "seattle-city-light",
        "pse",
        "snohomish-pud",
        "tacoma-power",
        "other"
      ],
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 92 lines
  • request_walkthrough unknown never probed

    Request an on-site walkthrough at 1-5 times the person proposes: 24 h to 60 days out, starting Mon-Fri 8 AM-4 PM or Sat 9 AM-12 PM Pacific. Kolmo confirms one within 1 business day; until then it is "requested", not "booked". Without quoteLink, pass the person's own name, email, phone, address and scope. dryRun: true previews.

    mcp-tool

    {
  "type": "object",
  "required": [
    "proposedTimes"
  ],
  "properties": {
    "name": {
      "type": "string",
      "minLength": 1
    },
    "email": {
      "type": "string",
      "format": "email"
    },
    "notes": {
      "type": "string",
      "maxLength": 2000,
      "description": "Access, parking, pets"
    },
    "phone": {
      "type": "string",
      "minLength": 7
    },
    "scope": {
      "type": "string",
      "minLength": 10
    },
    "dryRun": {
      "type": "boolean"
    },
    "address": {
      "type": "string",
      "minLength": 5,
      "description": "Property street address and city"
    },
    "quoteLink": {
      "type": "string",
      "maxLength": 300,
      "minLength": 36,
      "description": "The person's kolmo.io/quotes/<id> link, as Kolmo sent it. Never guess one."
    },
    "proposedTimes": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 5,
      "minItems": 1,
      "description": "ISO 8601 with offset"
    }
  },
  "additionalProperties": false
}
    arguments 53 lines
  • get_my_quote unknown 17h ago

    Read the quote Kolmo sent the person: scope, line items, options, total, payment schedule, expiry and whether it can still be accepted. Call before respond_to_quote.

    mcp-tool

    {
  "type": "object",
  "required": [
    "quoteLink"
  ],
  "properties": {
    "quoteLink": {
      "type": "string",
      "maxLength": 300,
      "minLength": 36,
      "description": "The person's kolmo.io/quotes/<id> link, as Kolmo sent it. Never guess one."
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • respond_to_quote unknown never probed

    Answer a Kolmo quote for the person. "accepted" binds them to the work at that total; "declined" is final; "changes_requested" keeps it open and needs notes. To accept: show the person scope, options and total from get_my_quote, get an explicit yes, pass that total as confirmedTotal.

    mcp-tool

    {
  "type": "object",
  "required": [
    "quoteLink",
    "response"
  ],
  "properties": {
    "notes": {
      "type": "string",
      "maxLength": 5000
    },
    "response": {
      "enum": [
        "accepted",
        "declined",
        "changes_requested"
      ],
      "type": "string"
    },
    "quoteLink": {
      "type": "string",
      "maxLength": 300,
      "minLength": 36,
      "description": "The person's kolmo.io/quotes/<id> link, as Kolmo sent it. Never guess one."
    },
    "confirmedTotal": {
      "type": "number",
      "description": "Required to accept"
    },
    "personConfirmed": {
      "type": "boolean",
      "description": "True only after the person said yes. Required to accept or decline"
    },
    "selectedOptions": {
      "type": "object",
      "properties": {
        "alternates": {
          "type": "object",
          "description": "group → choice id",
          "additionalProperties": {
            "type": "integer"
          }
        },
        "optionalIds": {
          "type": "array",
          "items": {
            "type": "integer"
          }
        }
      },
      "additionalProperties": false
    }
  },
  "additionalProperties": false
}
    arguments 55 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 742c2dd0cee0c90d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/742c2dd0cee0c90d/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/742c2dd0cee0c90d/badge.svg)](https://brick.blue/agent/742c2dd0cee0c90d?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.