Skip to main content
Glama

LEVA building cost estimates

Estimate a building of a given size

estimate_build
Read-onlyIdempotent

What a LEVA building of a given size costs to build: total, materials, labour (execution) and hours in USD with a low-high range, from LEVA's priced reference designs of that product, plus the nearest reference design and a link that opens LEVA's 3D configurator at exactly that size with an itemized bill of materials. Use it for questions like 'how much does a 20 x 30 ft ADU / 12 x 16 shed / barndominium cost to build'. Estimates, not quotes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "product": "<product>"
    },
    "name": "estimate_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoinstead of width and length: the floor area (sq ft, or m2 with unit m)
roofNooptional roof shape: gable, hip, halfhip, mono, flat
unitNounit of width / length / area (default ft)
widthNofootprint width
lengthNofootprint length
marketNooptional two-letter country code for local material prices, e.g. DE, GB, CA
productYesthe product handle from list_products, e.g. adu, barndominium, shed, sauna-1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, and the description adds real substance on top: results are derived from LEVA's priced reference designs, come as a low-high range in USD, include the nearest reference design (implying approximation when the exact size isn't catalogued), and include a configurator deep link with an itemized BOM. The 'estimates, not quotes' caveat is a useful accuracy disclosure. It stops short of stating precision, rounding, or latency.

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?

Front-loads the cost answer and return payload before the usage examples, with no filler sentences. The first sentence is long and comma-stacked, which slightly hurts scanability, but every clause carries information.

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

Completeness4/5

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

With no output schema, the description does the necessary work of describing the return payload in detail, and it covers the required-product dependency. For a 7-parameter estimation tool the only residual gap is handling of unmatched sizes and currency/unit interaction, which the 'nearest reference design' phrasing partially covers.

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

Parameters3/5

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

Schema description coverage is 100%, so width, length, area, unit, roof, market, and product are all already documented, and the description adds only the product-handle provenance hint that the schema itself states. It does not clarify the width/length vs area alternative or how unit 'm' interacts with market pricing beyond what the schema says. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('What a LEVA building of a given size costs to build') and enumerates exactly what is returned: total, materials, labour, hours, USD low-high range, nearest reference design, and a 3D configurator link. This clearly separates it from sibling lookups like get_product_prices or get_item_prices, which are price-listing rather than size-based estimation.

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

Usage Guidelines4/5

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

Gives concrete trigger questions ('how much does a 20 x 30 ft ADU / 12 x 16 shed / barndominium cost to build') and a scope caveat ('Estimates, not quotes'), plus points to list_products as the source of the required product handle. It does not explicitly say when to prefer get_product_prices or get_item_prices instead, so the routing is clear but not exclusionary.

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.

Resources