bimhouse
bim.house — words become buildings. Generate BIM, check code & structure, quote materials.
¿Debería usar esto?
Calidad y seguridad
Hallazgos (5)
- HIGH
- MEDIUMen list_incomplete_addresses
- MEDIUMen place_in_house
- LOWen register_contractor
- INFOen list_incomplete_addresses
Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.
Costo de contexto
Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.
Instalar
Instalación con un clic
Agrega esto a tu archivo `claude_desktop_config.json`:
{
"mcpServers": {
"bimhouse": {
"url": "https://bim.house/mcp"
}
}
}Puntos de conexión remotos
https://bim.house/mcpstreamable-httpQué puede hacer
Inventario de herramientas
Herramientas (29)
⚪whoami
[EN] Verify API-key auth: returns your account email if a valid Bearer key is sent. / API キー認証の確認。Authorization: Bearer <APIキー> (/console で発行) を付けると認証済みアカウントの email を返す。Web/CLI どちらからでも使える。
Esquema de entrada
{
"type": "object",
"properties": {}
}⚪chat(history, message)
[EN] AI chat about architecture/BIM/code/MU. Requires Bearer API key; first ¥300 (5 calls) free. / bim.house / MU の AI チャット。メール認証して /console で発行した API キーで認証必須 (Authorization: Bearer <APIキー>)。未チャージでも初回 ¥300 分 (5 回) は無料、使い切ったら /credits でチャージ。建築・BIM・法規・SIPs・MU について日本語で答える。引数 message (必須) と history (任意, [{role, content}])。
Esquema de entrada
{
"type": "object",
"properties": {
"history": {
"description": "直前までの会話履歴 (任意)",
"items": {
"properties": {
"content": {
"type": "string"
},
"role": {
"type": "string"
}
},
"type": "object"
},
"type": "array"
},
"message": {
"description": "ユーザーの質問・メッセージ",
"type": "string"
}
},
"required": [
"message"
]
}🟢search_catalog(brand, category, limit, q)
[EN] Search the building-materials catalog (3,900+ SKUs) by keyword/brand/category. / bim.house の建材・設備カタログ (3,900+ SKU) を検索。窓/断熱/設備/家具などを brand・category・キーワードで絞り込む。
Esquema de entrada
{
"type": "object",
"properties": {
"brand": {
"description": "ブランド完全一致 (例: YKK AP, LIXIL)",
"type": "string"
},
"category": {
"description": "カテゴリ完全一致 (例: 窓, 断熱材, 設備)",
"type": "string"
},
"limit": {
"description": "最大件数 (1-50, 既定 20)",
"type": "integer"
},
"q": {
"description": "キーワード (商品名・型番・JAN・タグを部分一致)",
"type": "string"
}
}
}🟢get_product(sku)
[EN] Get one product's full detail by SKU (price, U-value/η, stock, JAN, successor). / SKU を指定して 1 製品の詳細 (価格・性能値 U値/η値・在庫・JAN・後継品) を取得。
Esquema de entrada
{
"type": "object",
"properties": {
"sku": {
"description": "製品 SKU",
"type": "string"
}
},
"required": [
"sku"
]
}🟡list_houses(include_user)
[EN] List curated public houses (famous buildings, landmarks); set include_user=true for public user houses. / 運営 curated 公開物件 (有名建築・巨大ランドマーク・SOLUNA 等) の一覧。slug / 規模 / 要素数 / bim.json 充足率(%) を返す。ユーザー作成物件 (u-*) は既定では含まない (直リンクで個別取得は可)。include_user=true で公開ユーザー物件も含める。
Esquema de entrada
{
"type": "object",
"properties": {
"include_user": {
"description": "公開 (private=false) のユーザー作成物件も含める (既定 false)",
"type": "boolean"
}
}
}🟢get_house_bim(include_elements, slug)
[EN] Fetch a house's full bim.json v1 (project meta + elements) by slug. / slug を指定して物件の完全な bim.json v1 (project メタ + elements 配列) を取得。include_elements=false でメタのみ。
Esquema de entrada
{
"type": "object",
"properties": {
"include_elements": {
"description": "elements を含めるか (既定 true)",
"type": "boolean"
},
"slug": {
"description": "物件 slug (list_houses 参照)",
"type": "string"
}
},
"required": [
"slug"
]
}🟢houki_check(slug)
[EN] Run the Japanese Building Standards Act check (coverage, FAR, slopes, daylight, ventilation) and return pass/fail. / 建築基準法チェック (建ぺい率・容積率・北側/道路斜線・採光・換気) を houki-engine で実行し合否を返す。
Esquema de entrada
{
"type": "object",
"properties": {
"slug": {
"description": "物件 slug",
"type": "string"
}
},
"required": [
"slug"
]
}⚪material_quote(slug)
[EN] Catalog-priced cost estimate: BOM, total, ¥/m², lead times and critical path from the BIM takeoff. / カタログ連携の概算見積もり。BIM 要素 takeoff × 建材カタログ実価格 (窓/ドア/設備) + 原単位 (躯体/仕上げ) で BOM・総額・㎡単価を算出し、各資材の納期 (lead_time_days) と在庫、クリティカルパス納期も返す。
Esquema de entrada
{
"type": "object",
"properties": {
"slug": {
"description": "物件 slug",
"type": "string"
}
},
"required": [
"slug"
]
}🟡create_house(address, construction_jpy, elements, existing_year_built, floors, ...)
[EN] Build a new house (bim.json) from an address alone (geocoded, auto-named, climate-aware) or full elements; returns slug + edit_token + viewer/permit URLs + inline houki & structure verdicts. No auth (private by default, rate-limited). / 新しい物件 (bim.json) を作成する。name か address のどちらか必須 — 住所だけ渡せば geocode で座標を引き「<地名>の家」と自動命名して家が建つ (REINFOLIB_KEY 設定時は用途地域も実値注入)。elements (bim.json v1 要素配列) を渡すとそのまま保存、省略すると敷地寸法から住宅 BIM を自動生成。name/rooms に「薪ストーブ・土間・ロフト・カーポート・書斎・ピアノ・サウナ」等の言葉が入ると対応する要素 (煙突・炉台・はしご込み) を自動配置し、寒冷地住所ならトリプルガラス+付加断熱+雪止めに外皮を格上げ。「平屋」「2階建て」も階数に反映。slug と edit_token、viewer/json/permit URL と適用 features・site (座標/用途地域ソース) を返す。
Esquema de entrada
{
"type": "object",
"properties": {
"address": {
"description": "所在地 (これだけでも家が建つ。geocode で座標解決・気候/積雪も住所から自動設定)",
"type": "string"
},
"construction_jpy": {
"description": "概算工事費 円",
"type": "integer"
},
"elements": {
"description": "bim.json v1 要素配列。各要素 {id,cls,label,descr,shape:'box'|'cylinder',x,y,z,w,d,h,rotation?} (mm)。省略可。",
"items": {
"type": "object"
},
"type": "array"
},
"existing_year_built": {
"description": "既存建物の建築年 (西暦)。1981年5月以前は旧耐震 (耐震診断推奨)、2006年以前(または未指定)はアスベスト事前調査を概算に自動計上する。project_type=renovation|change_of_use のときのみ使う。",
"type": "integer"
},
"floors": {
"description": "階数 (既定 1)",
"type": "integer"
},
"gross_m2": {
"description": "延床面積 ㎡",
"type": "number"
},
"land_area_m2": {
"description": "敷地面積 ㎡",
"type": "number"
},
"lot_d_m": {
"description": "奥行 m (簡易シェル生成に使用)",
"type": "number"
},
"lot_w_m": {
"description": "間口 m (簡易シェル生成に使用)",
"type": "number"
},
"name": {
"description": "物件名 (address を渡せば省略可 — 地名から自動命名)",
"type": "string"
},
"private": {
"description": "true で物件一覧 (/property) に非掲載・直リンクのみ。既定 false=掲載。",
"type": "boolean"
},
"project_type": {
"description": "[EN] 'new' (default) builds a from-scratch cost estimate. 'renovation'/'change_of_use' treat this as an EXISTING building being remodeled: foundation/frame/roof default to ¥0 (reused as-is) and only the trades in renovation_scope are costed at renovation unit rates. / 既定は new=新築(ゼロから建てる前提の概算)。renovation/change_of_use を指定すると『既存建物の改修』として扱われ、基礎・躯体・屋根等は既定でコスト¥0(既存流用)になり、renovation_scope で指定した工種だけを改修単価で見積もる。get_build_plan の結果も新築フル工程でなく改修工程 (解体・調査系を含む) に切り替わる。",
"enum": [
"new",
"renovation",
"change_of_use"
],
"type": "string"
},
"renovation_scope": {
"description": "改修対象の工種 code 配列 (demo/interior/fittings/electrical/plumbing/hvac/roof/exterior/frame/found/temp/pv)。project_type=renovation|change_of_use のときのみ有効。省略時は典型的なフルリノベ (demo+内装+建具+電気+給排水+空調) を既定スコープとして使う。",
"items": {
"type": "string"
},
"type": "array"
},
"renovation_scope_m2": {
"description": "実際に改修する範囲の面積㎡ (例: 3階建282㎡の建物のうち1階94㎡だけ改修するなら94)。省略時は gross_m2 (建物全体) を使う。project_type=renovation|change_of_use のときのみ有効。",
"type": "number"
},
"rooms": {
"description": "室構成サマリー",
"type": "string"
},
"seismic_retrofit": {
"description": "true で耐震補強費 (建物全体延床×単価) を概算に含める。project_type=renovation|change_of_use のときのみ使う。",
"type": "boolean"
},
"structure": {
"description": "構造 (例: RC 打放しコンクリート)",
"type": "string"
},
"zoning": {
"description": "用途地域 (例: 近隣商業地域)",
"type": "string"
}
},
"required": []
}🟡create_product(brand, category, description, eta_value, ifc_class, ...)
[EN] Register a new catalog product SKU (needs Bearer API key; insert-only, no overwrite). / 建材カタログ (products) に新しい製品 SKU を登録する。サッシ/窓/断熱材/照明/設備/家具/ドア等。Authorization: Bearer <APIキー> (/console で発行) が必須。登録後は /catalog と search_catalog に即反映。既存 SKU の上書きは不可 (insert-only)。
Esquema de entrada
{
"type": "object",
"properties": {
"brand": {
"description": "ブランド (例: YKK AP, LIXIL)",
"type": "string"
},
"category": {
"description": "カテゴリ (必須)。例: サッシ, 窓, 断熱材, 照明, 設備, 家具, ドア",
"type": "string"
},
"description": {
"description": "製品説明",
"type": "string"
},
"eta_value": {
"description": "日射熱取得率 η値",
"type": "number"
},
"ifc_class": {
"description": "IFC クラス (省略時はカテゴリから推定。例: IFCWINDOW)",
"type": "string"
},
"install_jpy": {
"description": "施工費の目安 円",
"type": "integer"
},
"jan_code": {
"description": "JAN コード",
"type": "string"
},
"lead_time_days": {
"description": "納期 (日)",
"type": "integer"
},
"mfr_code": {
"description": "メーカー型番",
"type": "string"
},
"name": {
"description": "製品名 (必須)",
"type": "string"
},
"price_jpy": {
"description": "メーカー希望小売 税抜 円",
"type": "integer"
},
"sku": {
"description": "一意な SKU (英数・- _ . 、64字以内)。例: YKK-APW330-W",
"type": "string"
},
"spec": {
"description": "追加スペック (任意の key/value オブジェクト)",
"type": "object"
},
"stock_status": {
"description": "在庫 (in_stock/low_stock/order/made_to_order/discontinued。既定 in_stock)",
"type": "string"
},
"tags": {
"description": "カンマ区切りタグ",
"type": "string"
},
"u_value": {
"description": "熱貫流率 U値 W/m²K",
"type": "number"
},
"url": {
"description": "メーカー公式ページ URL",
"type": "string"
},
"warranty_years": {
"description": "保証年数",
"type": "integer"
}
},
"required": [
"sku",
"name",
"category"
]
}🟡update_product(brand, category, description, eta_value, install_jpy, ...)
[EN] Update fields of a product you created (needs Bearer API key; your SKUs only). / 自分が create_product で登録した製品のフィールドを更新する。Authorization: Bearer <APIキー> 必須。他者/公式 SKU は更新不可。指定したフィールドのみ上書き。
Esquema de entrada
{
"type": "object",
"properties": {
"brand": {
"type": "string"
},
"category": {
"type": "string"
},
"description": {
"type": "string"
},
"eta_value": {
"type": "number"
},
"install_jpy": {
"type": "integer"
},
"jan_code": {
"type": "string"
},
"lead_time_days": {
"type": "integer"
},
"mfr_code": {
"type": "string"
},
"name": {
"type": "string"
},
"price_jpy": {
"type": "integer"
},
"sku": {
"description": "更新対象の SKU (必須)",
"type": "string"
},
"spec": {
"description": "追加スペック (上書き)",
"type": "object"
},
"stock_status": {
"description": "in_stock/low_stock/order/made_to_order/discontinued",
"type": "string"
},
"tags": {
"type": "string"
},
"u_value": {
"type": "number"
},
"url": {
"type": "string"
},
"warranty_years": {
"type": "integer"
}
},
"required": [
"sku"
]
}🟢list_mine
[EN] List products you registered (needs Bearer API key). / 自分 (API キーのアカウント) が登録した製品の一覧を返す。Authorization: Bearer <APIキー> 必須。
Esquema de entrada
{
"type": "object",
"properties": {}
}⚪retire_product(sku)
[EN] Retire (discontinue) a product you created (needs Bearer API key; soft, not hard delete). / 自分が登録した製品を取り下げる (生産終了化。ハード削除はしない)。Authorization: Bearer <APIキー> 必須。他者/公式 SKU は不可。
Esquema de entrada
{
"type": "object",
"properties": {
"sku": {
"description": "取り下げる SKU (必須)",
"type": "string"
}
},
"required": [
"sku"
]
}🟡update_house(edit_token, elements, elements_json, note, project, ...)
[EN] Update an existing house's bim.json (needs edit_token): swap elements or patch project meta; returns a re-run houki verdict. Versioned each save. / 既存物件の bim.json を更新する。edit_token (create_house の返り値) が必要。elements (bim.json v1 要素配列) を渡すと差し替え、project (object) でメタ (name/construction_jpy/proposed_gross_m2 等) のみ更新も可。get_house_bim で現状を取得 → 編集 → update_house → 返り値の houki (法規再判定) を確認、のループで自分の LLM だけで設計改善が完結する。保存ごとに履歴 (bim_versions) が残る。
Esquema de entrada
{
"type": "object",
"properties": {
"edit_token": {
"description": "create_house が返した edit_token (必須)",
"type": "string"
},
"elements": {
"description": "bim.json v1 要素配列 (全置換)。省略時は既存要素を維持",
"type": "array"
},
"elements_json": {
"description": "elements の JSON 文字列版 (strict-schema クライアント用)",
"type": "string"
},
"note": {
"description": "変更メモ (履歴に残る・500字まで)",
"type": "string"
},
"project": {
"description": "メタ更新 (name / construction_jpy / proposed_gross_m2 / proposed_floors / proposed_structure / proposed_rooms / project_type['new'|'renovation'|'change_of_use'] / renovation_scope[配列] / renovation_scope_m2 / existing_year_built / seismic_retrofit)。project_type を renovation|change_of_use に変えると、以後この物件の get_build_plan/cost.json は改修工程・改修単価で再計算される (基礎・躯体等は既定でコスト¥0=既存流用)。",
"type": "object"
},
"slug": {
"description": "物件 slug (必須)",
"type": "string"
}
},
"required": [
"slug",
"edit_token"
]
}🟡set_visibility(edit_token, private, slug)
[EN] Toggle a house's public listing on/off (needs edit_token). / 物件の掲載/非掲載を切り替える。edit_token (create_house の返り値) が必要。private=true で物件一覧から非掲載 (直リンクは残る)。進化ループの低スコア物件の淘汰などに使う。
Esquema de entrada
{
"type": "object",
"properties": {
"edit_token": {
"description": "create_house が返した edit_token (必須)",
"type": "string"
},
"private": {
"description": "true=非掲載 / false=掲載",
"type": "boolean"
},
"slug": {
"description": "物件 slug (必須)",
"type": "string"
}
},
"required": [
"slug",
"edit_token",
"private"
]
}🟡place_in_house(edit_token, ref, room, slug, source)
[EN] Place a *live reference* to another service's catalog into a house (needs edit_token) — not a copy. source 'mu' refs a wearmu.com brand slug (goods made by MU); source 'device' refs a device.house room key (word-driven hardware). The viewer / GET /api/projects/<slug>/furnishings resolves these at view time so stock is always live and never duplicated. / 家に MU(wearmu.com の作ったもの) や device.house(言葉で動く実機) の在庫を *参照* で置く。edit_token 必須。複製せずポインタだけ持ち、表示時に各サービスをライブ解決する(常に最新・売れたら消える)。source='mu' は brand slug(例 biruwa)、source='device' は部屋キー(entrance/living/bedroom/kitchen/outdoor/any)。
Esquema de entrada
{
"type": "object",
"properties": {
"edit_token": {
"description": "create_house が返した edit_token (必須)",
"type": "string"
},
"ref": {
"description": "mu: brand slug (例 biruwa, mcp) / device: 部屋キー (living 等)",
"type": "string"
},
"room": {
"description": "家の中の置き場所 (表示用・任意)",
"type": "string"
},
"slug": {
"description": "物件 slug (必須)",
"type": "string"
},
"source": {
"description": "'mu'=wearmu.com / 'device'=device.house",
"enum": [
"mu",
"device"
],
"type": "string"
}
},
"required": [
"slug",
"edit_token",
"source",
"ref"
]
}🟡set_forkable(edit_token, forkable, slug)
[EN] Allow or forbid others from forking (copying) a house (needs edit_token). / 他者がこの物件をフォーク (コピー) できるかを切り替える。edit_token が必要。forkable=false で他者のコピー作成を禁止 (既定は全て可)。
Esquema de entrada
{
"type": "object",
"properties": {
"edit_token": {
"description": "create_house が返した edit_token (必須)",
"type": "string"
},
"forkable": {
"description": "true=フォーク可 (既定) / false=フォーク不可",
"type": "boolean"
},
"slug": {
"description": "物件 slug (必須)",
"type": "string"
}
},
"required": [
"slug",
"edit_token",
"forkable"
]
}🟢get_houki_rules(slug)
[EN] List the building-code checks the engine runs (law refs) + any active zoning-rule overrides; pass slug to also get that house's effective site conditions + houki verdict. / houki エンジンがチェックする法規項目 (根拠条文) と、登録済みの用途地域規制ルール上書き一覧を返す。slug を渡すとその物件の有効敷地条件 + 法規判定も同梱。
Esquema de entrada
{
"type": "object",
"properties": {
"slug": {
"description": "任意。指定すると有効敷地条件 + houki 判定も返す",
"type": "string"
}
}
}🟢get_site_context(slug)
[EN] Get a house's effective site conditions used by houki_check (zoning, road width, high/fire district, climate zone, latitude, neighbor setback, min lot area, shadow regulation). / houki_check が使う物件の有効敷地条件を取得 (用途地域・道路幅員・高度/防火地区・気候区分・緯度・隣地距離・敷地面積最低限度・日影規制)。
Esquema de entrada
{
"type": "object",
"properties": {
"slug": {
"description": "物件 slug (必須)",
"type": "string"
}
},
"required": [
"slug"
]
}🟡set_site_context(climate_zone, edit_token, fire_district, high_district, latitude, ...)
[EN] Override a house's site conditions for houki_check (needs edit_token). Only provided fields are updated; returns the re-run houki verdict. Fixes false NGs from assumed defaults (e.g. set the real road width). / 物件の敷地条件を上書きして houki_check に反映する。edit_token 認証が必要。指定したフィールドのみ更新し、再判定した houki を返す。既定値による誤 NG (例: 前面道路幅員) を実値で是正できる。
Esquema de entrada
{
"type": "object",
"properties": {
"climate_zone": {
"description": "省エネ地域区分 1-8",
"type": "integer"
},
"edit_token": {
"description": "create_house が返した edit_token (必須)",
"type": "string"
},
"fire_district": {
"description": "防火地域 / 準防火地域",
"type": "string"
},
"high_district": {
"description": "高度地区 (例: 第1種高度地区)",
"type": "string"
},
"latitude": {
"description": "緯度 (日影計算用)",
"type": "number"
},
"min_lot_area_m2": {
"description": "敷地面積の最低限度 (㎡)",
"type": "number"
},
"neighbor_setback_m": {
"description": "隣地境界距離 (m) — 隣地斜線",
"type": "number"
},
"north_setback_m": {
"description": "北側隣地距離 (m)",
"type": "number"
},
"road_width_m": {
"description": "前面道路幅員 (m) — 道路斜線・容積率低減に効く",
"type": "number"
},
"shadow_regulation": {
"description": "日影規制の条例値 {measurement_height_m, limit_5m_h, limit_10m_h, start_hour, end_hour}。省略時は用途地域+規模で自動判定",
"type": "object"
},
"slug": {
"description": "物件 slug (必須)",
"type": "string"
},
"zoning": {
"description": "用途地域 (例: 第一種住居地域)",
"type": "string"
}
},
"required": [
"slug",
"edit_token"
]
}🟡admin_set_site_context(admin_token, entries, slug)
[EN] Bulk-set site conditions for any houses (admin only, admin_token; no edit_token). Pass `entries`: [{slug, zoning?, road_width_m?, high_district?, fire_district?, climate_zone?, latitude?, neighbor_setback_m?, min_lot_area_m2?, shadow_regulation?}]. DB + cache applied immediately. For operators to backfill zoning/road-width (e.g. from reinfolib) across all properties. / 任意の物件の敷地条件を一括上書き (管理者のみ・edit_token 不要)。entries 配列で複数物件をまとめて投入。DB+キャッシュ即時反映。用途地域/道路幅員等の実データを全物件へ流し込む運用者向け。
Esquema de entrada
{
"type": "object",
"properties": {
"admin_token": {
"description": "管理者トークン (必須)",
"type": "string"
},
"entries": {
"description": "物件ごとの敷地条件。各要素は {slug(必須), zoning?, road_width_m?, north_setback_m?, neighbor_setback_m?, high_district?, fire_district?, climate_zone?, latitude?, min_lot_area_m2?, shadow_regulation?}",
"items": {
"properties": {
"slug": {
"type": "string"
}
},
"required": [
"slug"
],
"type": "object"
},
"type": "array"
},
"slug": {
"description": "単一指定する場合 (entries の代わり)",
"type": "string"
}
},
"required": [
"admin_token"
]
}🟢list_incomplete_addresses(admin_token, limit)
[EN] List public houses whose address is incomplete (missing town name / placeholder), so they can be corrected — admin only. Fixing them lets zoning be derived from coordinates. / 住所が不完全 (町名欠落・プレースホルダ) な公開物件を一覧する。管理者のみ。直すと座標から用途地域を判定でき投入できる。
Esquema de entrada
{
"type": "object",
"properties": {
"admin_token": {
"description": "管理者トークン (必須)",
"type": "string"
},
"limit": {
"description": "返す最大件数 (既定200・最大2000)",
"type": "integer"
}
},
"required": [
"admin_token"
]
}⚪upsert_zoning_rule(absolute_height_limit_mm, admin_token, coverage_pct, far_pct, far_road_coefficient, ...)
[EN] Add/update a zoning regulation rule (coverage/FAR/slope/height limits) — admin only (admin_token). Applies to all houses matching (profile, zoning). / 用途地域の規制ルール (建ぺい/容積/斜線/高さ等) を追加・更新する。管理者のみ (admin_token)。(profile, zoning) に一致する全物件の houki に反映。
Esquema de entrada
{
"type": "object",
"properties": {
"absolute_height_limit_mm": {
"description": "絶対高さ制限 mm (null=なし)",
"type": "integer"
},
"admin_token": {
"description": "管理者トークン (必須)",
"type": "string"
},
"coverage_pct": {
"description": "建ぺい率上限 %",
"type": "number"
},
"far_pct": {
"description": "指定容積率 %",
"type": "number"
},
"far_road_coefficient": {
"description": "前面道路幅員 容積率低減係数 (住居0.4/他0.6)",
"type": "number"
},
"north_slope_start_mm": {
"description": "北側斜線起点高 mm (null=適用外)",
"type": "integer"
},
"profile": {
"description": "法域 (既定 Japan)。例: Japan / SpainCatalonia / UsaHawaii / France",
"type": "string"
},
"road_applicable_distance_m": {
"description": "道路斜線適用距離 (m)",
"type": "number"
},
"road_slope_d": {
"description": "道路斜線勾配 分母 (1.25=4)",
"type": "integer"
},
"road_slope_n": {
"description": "道路斜線勾配 分子 (1.25=5)",
"type": "integer"
},
"zoning": {
"description": "用途地域名 (部分一致キー。例: 第一種住居)",
"type": "string"
}
},
"required": [
"admin_token",
"zoning"
]
}🔴delete_zoning_rule(admin_token, profile, zoning)
[EN] Remove a zoning rule override (reverts to engine defaults) — admin only. / 用途地域規制ルールの上書きを削除し、エンジン既定値に戻す。管理者のみ。
Esquema de entrada
{
"type": "object",
"properties": {
"admin_token": {
"description": "管理者トークン (必須)",
"type": "string"
},
"profile": {
"description": "法域 (既定 Japan)",
"type": "string"
},
"zoning": {
"description": "用途地域名",
"type": "string"
}
},
"required": [
"admin_token",
"zoning"
]
}🟢get_build_plan(slug)
[EN] Construction plan for a house: schedule (Gantt) + per-trade order packages (cost, lead, region-driven spec constraints, inspection checklist). / 物件の施工計画。工種(こうしゅ)別に 工程(ガント) + 発注パッケージ(概算・工期・地域由来の仕様制約・検査チェックリスト) を返す。見積を工種に割って自動生成。
Esquema de entrada
{
"type": "object",
"properties": {
"slug": {
"description": "物件 slug",
"type": "string"
}
},
"required": [
"slug"
]
}⚪match_contractors(slug, trade)
[EN] Match contractors to a house by trade × location (prefecture or lat/lng+radius). One house's order naturally splits across local builders. / 工種 × 場所 (都道府県 or 緯度経度+対応半径) で業者をマッチ。trade 省略で全工種を一括。1棟の発注が地域の複数業者に自然に分かれる。
Esquema de entrada
{
"type": "object",
"properties": {
"slug": {
"description": "物件 slug",
"type": "string"
},
"trade": {
"description": "工種 code (任意): temp/found/frame/roof/exterior/fittings/electrical/plumbing/hvac/interior/pv/inspection",
"type": "string"
}
},
"required": [
"slug"
]
}🟢list_contractors(prefecture, trade)
[EN] List registered contractors, optionally filtered by prefecture/trade. / 登録業者の一覧。都道府県・工種で絞り込み可。
Esquema de entrada
{
"type": "object",
"properties": {
"prefecture": {
"description": "都道府県 (任意, 例: 北海道)",
"type": "string"
},
"trade": {
"description": "工種 code (任意)",
"type": "string"
}
}
}⚪register_contractor(contact, fulfillment, lat, lead_time_days, lng, ...)
[EN] Register a contractor (supply side, self-serve). Requires Bearer API key. trades = trade codes or 'all'; location via prefectures and/or lat/lng+service_radius_km. / 業者を登録 (供給側セルフサーブ・API キー必須)。trades=工種 code 配列か 'all'、場所は prefectures か lat/lng+service_radius_km。
Esquema de entrada
{
"type": "object",
"properties": {
"contact": {
"description": "連絡先 (メール等)",
"type": "string"
},
"fulfillment": {
"description": "labor / kit / both (既定 labor)",
"type": "string"
},
"lat": {
"description": "拠点 緯度 (任意)",
"type": "number"
},
"lead_time_days": {
"description": "標準納期 日数 (任意)",
"type": "integer"
},
"lng": {
"description": "拠点 経度 (任意)",
"type": "number"
},
"name": {
"description": "業者名 (必須)",
"type": "string"
},
"prefectures": {
"description": "対応都道府県",
"items": {
"type": "string"
},
"type": "array"
},
"service_radius_km": {
"description": "対応半径 km (任意)",
"type": "number"
},
"trades": {
"description": "対応工種 code の配列、または 'all'",
"items": {
"type": "string"
},
"type": "array"
}
},
"required": [
"name"
]
}🟡place_order(contractor_id, slug, trade)
[EN] Create a DRAFT purchase order for one trade of a house to a contractor (does NOT send anything — human sends later). / 物件の1工種を業者へ発注 (ドラフト作成のみ・⚠送信はしない)。spec/検査リストを同梱。
Esquema de entrada
{
"type": "object",
"properties": {
"contractor_id": {
"description": "match_contractors / list_contractors の contractor_id",
"type": "integer"
},
"slug": {
"description": "物件 slug",
"type": "string"
},
"trade": {
"description": "工種 code (get_build_plan の phases.trade)",
"type": "string"
}
},
"required": [
"slug",
"trade",
"contractor_id"
]
}Comunidad
Evidencia