Skip to main content
Glama

Seattle cost estimate

get_estimate
Read-onlyIdempotent

Seattle cost estimate: range, material/labor split, days, line items.

?=optional; (mat)=get_material_options ID (a unique close name also resolves; an ambiguous one lists candidates).

interior-painting: rooms([{id,name,length,width(ft),height(6-30),paintCeiling,paintTrim,doorCount,windowCount,surfaceCondition(new-drywall|good-condition|poor-condition),trimComplexity(baseboards-only|simple-trim|complex-trim),wallTexture(smooth|light-texture|heavy-texture),roomEmpty}]); paintQuality(mat); paintFinish(flat|eggshell|satin|semi-gloss|gloss); includesPrimer; majorColorChange?(+colorChange{currentColor,targetColor}) exterior-painting: wallArea,trimArea(sqft); doorCount; paintQuality(mat); surfacePrepLevel(minimal|moderate|extensive); includesPrimer; stories?(1-3); colorChange?(+colorChangeData{currentColor,targetColor}) flooring: rooms([{id,name,length,width(ft)}]); flooringMaterial(mat); includesUnderlayment,includesBaseboard,includesRemoval,includesSubfloorPrep; underlaymentType?,baseboardType?(mat); baseboardLinearFeet?(default perimeter); removalType?(carpet|tile|hardwood); transitionCount? deck: deckType(new|existing); dimensions({length,width≤200,height≤30 ft}); deckingMaterial(mat: composite-decking…); framingMaterial(mat); includesRailing,includesStairs; railingMaterial?,finishType?(mat); railingLinearFeet?; stairSteps?(1-30); landingRequired?; deckShape?(rectangle|l-shape|angled-corners|multi-level); skirtingType?(none|lattice|matching-board); existingDeckWorkItems?(existing: ≥1 of stainOrSeal,inspection,replaceFlooring(+_area),replacePosts(+_count),addOrReplaceRailing(+_linearFeet),repairFraming(+_area)) windows: windows([{id,windowType(double-hung|single-hung|casement|slider|awning|picture|bay|bow or row id),width,height(12-120 in),quantity}]); qualityLevel(standard|premium|luxury → vinyl|fiberglass|wood-clad); includesTrimWork,includesRemoval,energyEfficient; trimMaterial?(mat) siding: wallArea(sqft); sidingMaterial(mat); homeHeight(single-story|two-story|three-story); includesInsulation,includesRemoval,soffit; insulationType?(mat); existingSidingType?; trimLinearFeet; soffitLinearFeet?(with soffit) fence: linearFeet; fenceMaterial(mat); height(3-8 ft); gateCount; gateWidth?(ft); style?; terrain(flat|sloped|mixed); includesRemoval,concreteFootings landscaping: yardArea(sqft); includesIrrigation,includesSod,includesMulch,includesSitePrep; irrigationType?; irrigationZones?(with irrigation); sodSquareFeet?(with sod); mulchSquareFeet?(default yardArea); plants?([{id,plantType,quantity,size(small|medium|large)}]); hardscapeFeatures?([{id,featureType,squareFeet,material}]) kitchen: kitchenSize(40-600 sqft); scope(cosmetic|standard|full-gut); cabinets(keep|reface|prefab|semi-custom|custom); countertop(keep|laminate|butcher-block|quartz|granite|marble); appliances(keep|budget|mid-range|premium); flooring(keep|lvp|tile|hardwood); backsplash?,plumbingRelocation?,electricalUpgrade?,island?,lighting? bathroom: bathroomType(half-bath|full-bath|primary-bath|accessible); bathroomSize(20-300 sqft); scope(cosmetic|standard|full-gut); showerTub(keep|tub-to-shower|walk-in-shower|tub-replacement|freestanding-tub); vanity(keep|budget|mid-range|premium); tileWork(none|floor-only|floor-and-shower|full-tile); heatedFloors?,newLighting?,ventilation?,plumbingRelocation? basement: basementSize(150-3000 sqft); scope(open-rec-room|standard-finish|full-suite); ceilingHeight(under-7ft|7-to-8ft|over-8ft); moistureCondition(dry|minor-dampness|active-water); egress(has-egress|needs-egress|not-required); bathroom(none|half-bath|full-bath); kitchenette(none|wet-bar|full-kitchenette); bedroomCount?; flooring(lvp|carpet|polished-concrete|tile); insulation(existing|walls-only|walls-and-ceiling); hvac(extend-existing|mini-split|none-needed); electricalSubpanel?,homeAgePre1978? adu: type(dadu|aadu|basement-conversion|garage-conversion); sizeSqft(200-1200, dadu ≤1000); finishTier(builder|standard|premium); dadu only: foundation?(slab|crawl|stem-wall),sitework?(minimal|standard|heavy),utilityRunFeet?,preApprovedPlan?; treeRemovalCount?; homeAgePre1978?(not dadu) ada: projectScope(single-room|whole-home|bathroom-specific); modifications({grabBars,walkInShower,widerDoorways,ramp,nonSlipFlooring,leverHandles,raisedToilet,rollUnderSink,accessibleCounters,stairLift}, ≥1 true); currentCondition(minor|moderate|major); homeStories?(1-3); 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)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectYesProject input fields — see tool description for required fields per projectType.
projectTypeYesThe type of project

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
excludesYesScope NOT priced here. Relay alongside any figure.
laborCostYes
lineItemsNo
totalCostYesPoint figure. Relay estimateRange instead — a single number reads as a quote.
permitCostNoPresent on deck, kitchen, bathroom, basement, adu and ada. Already inside totalCost.
attributionYes
projectTypeYes
materialCostYes
pricingBasisNo
calculatorUrlYes
estimateRangeNoPlanning range for Seattle-area work. This is what to relay, with its qualifier attached.
contingencyCostNoPresent on basement and adu. When set, a contingency is ALREADY in totalCost — do not add another.
getAccurateQuoteYes
timeEstimateDaysNo
contingencyGuidanceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / projectType / enum
      Previous value: -[
      -  "interior-painting",
      -  "exterior-painting",
      -  "flooring",
      -  "deck",
      -  "windows",
      -  "siding",
      -  "fence",
      -  "landscaping",
      -  "kitchen",
      -  "bathroom",
      -  "basement",
      -  "adu",
      -  "ada",
      -  "electrical",
      -  "plumbing",
      -  "garage-doors",
      -  "concrete",
      -  "insulation",
      -  "gutters"
      -]New value: +[
      +  "interior-painting",
      +  "exterior-painting",
      +  "flooring",
      +  "deck",
      +  "windows",
      +  "siding",
      +  "fence",
      +  "landscaping",
      +  "kitchen",
      +  "bathroom",
      +  "basement",
      +  "adu",
      +  "ada",
      +  "electrical",
      +  "plumbing",
      +  "garage-doors",
      +  "doors",
      +  "concrete",
      +  "insulation",
      +  "gutters"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / projectType / enum
      Previous value: -[
      -  "interior-painting",
      -  "exterior-painting",
      -  "flooring",
      -  "deck",
      -  "windows",
      -  "siding",
      -  "fence",
      -  "landscaping",
      -  "kitchen",
      -  "bathroom",
      -  "basement",
      -  "adu",
      -  "ada"
      -]New value: +[
      +  "interior-painting",
      +  "exterior-painting",
      +  "flooring",
      +  "deck",
      +  "windows",
      +  "siding",
      +  "fence",
      +  "landscaping",
      +  "kitchen",
      +  "bathroom",
      +  "basement",
      +  "adu",
      +  "ada",
      +  "electrical",
      +  "plumbing",
      +  "garage-doors",
      +  "concrete",
      +  "insulation",
      +  "gutters"
      +]
    • changedOutput schema / properties / permitCost / description
      Previous value: -"Present on basement and adu, where permit cost is inside totalCost."New value: +"Present on deck, kitchen, bathroom, basement, adu and ada. Already inside totalCost."
  3. Changed3 schema fields changed
    • changedInput schema / properties / projectType / enum
      Previous value: -[
      -  "interior-painting",
      -  "deck",
      -  "exterior-painting",
      -  "flooring",
      -  "windows",
      -  "siding",
      -  "fence",
      -  "landscaping",
      -  "kitchen",
      -  "bathroom",
      -  "ada"
      -]New value: +[
      +  "interior-painting",
      +  "exterior-painting",
      +  "flooring",
      +  "deck",
      +  "windows",
      +  "siding",
      +  "fence",
      +  "landscaping",
      +  "kitchen",
      +  "bathroom",
      +  "basement",
      +  "adu",
      +  "ada"
      +]
    • addedOutput schema / properties / contingencyCost
      Added value: +{
      +  "description": "Present on basement and adu. When set, a contingency is ALREADY in totalCost — do not add another.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / permitCost
      Added value: +{
      +  "description": "Present on basement and adu, where permit cost is inside totalCost.",
      +  "type": "number"
      +}
  4. Changed6 schema fields changed
    • 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"
      +]
  5. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": true,
      +  "properties": {
      +    "attribution": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "citeAs": {
      +          "description": "Ready-made citation line. Use verbatim.",
      +          "type": "string"
      +        },
      +        "contractorLicense": {
      +          "type": "string"
      +        },
      +        "note": {
      +          "type": "string"
      +        },
      +        "organization": {
      +          "type": "string"
      +        },
      +        "primarySource": {
      +          "description": "Present when Kolmo verified but does not author the fact — cite both.",
      +          "type": "string"
      +        },
      +        "retrievedFrom": {
      +          "type": "string"
      +        },
      +        "sourceUrl": {
      +          "description": "The specific page these facts render on. Link this, not the site root.",
      +          "type": "string"
      +        },
      +        "url": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "organization",
      +        "contractorLicense",
      +        "url",
      +        "sourceUrl",
      +        "citeAs",
      +        "retrievedFrom",
      +        "note"
      +      ],
      +      "type": "object"
      +    },
      +    "calculatorUrl": {
      +      "type": "string"
      +    },
      +    "contingencyGuidance": {
      +      "type": "string"
      +    },
      +    "estimateRange": {
      +      "description": "Planning range for Seattle-area work. This is what to relay, with its qualifier attached."
      +    },
      +    "excludes": {
      +      "description": "Scope NOT priced here. Relay alongside any figure.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "getAccurateQuote": {
      +      "type": "string"
      +    },
      +    "laborCost": {
      +      "type": "number"
      +    },
      +    "lineItems": {},
      +    "materialCost": {
      +      "type": "number"
      +    },
      +    "pricingBasis": {},
      +    "projectType": {
      +      "type": "string"
      +    },
      +    "timeEstimateDays": {},
      +    "totalCost": {
      +      "description": "Point figure. Relay estimateRange instead — a single number reads as a quote.",
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "projectType",
      +    "totalCost",
      +    "materialCost",
      +    "laborCost",
      +    "contingencyGuidance",
      +    "excludes",
      +    "calculatorUrl",
      +    "getAccurateQuote",
      +    "attribution"
      +  ],
      +  "type": "object"
      +}
  6. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, and non-destructive behavior, so the bar is lower. The description adds useful behavioral context beyond that: it returns a range rather than a fixed quote, includes material/labor split, days, and line items, and explains that material inputs can be resolved by get_material_options ID or close name, with ambiguous names triggering candidate lists.

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?

The description is long, but the length is justified by the need to document 20 project types. It front-loads the output summary and then organizes each project type's parameter grammar compactly; the dense notation is somewhat hard to scan, but every segment earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity, the description is remarkably complete: it covers all project types, required vs. optional inputs, constraints, defaults, and material references. An output schema exists, so the description does not need to explain return values; nothing essential for invoking the tool correctly appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema's coverage metric is 100%, the schema merely points to 'see tool description for required fields per projectType.' The description compensates massively by specifying per-project required fields, optional markers, units, ranges, defaults, enum-like values, and material-resolution behavior for all 20 project types.

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?

The description opens with 'Seattle cost estimate: range, material/labor split, days, line items,' which clearly identifies the tool as a cost estimator and previews its outputs. It is specific enough to distinguish from siblings like estimate_permit_fee or get_project_roi, though it lacks an explicit verb phrase like 'get a cost estimate for.'

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?

The description gives no explicit guidance on when to use this tool versus alternatives such as estimate_permit_fee or get_material_options. It implies the tool is for estimating Seattle project costs by listing 20 project types, but it never states conditions, exclusions, or when a sibling would be more appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.