floor-plan-pink.vercel.app WebMCP Tools, Schemas & Agent Capabilities

floor-plan-pink.vercel.app

live Unverified (seed import) AI & Agents 11 tools imperative implementation

A shared conceptual floor-planning workspace where humans draw directly on the canvas and agents work the same plans through semantic WebMCP tools.

First seen 2026-11-05 · Last seen 2026-11-05 · Source: webmcp.com

Answer 2 · Act 9 · Transact 0 · Score: Not yet scored

Tool inspector

replace_floorplan

act imperative

Redesign one specific plan from scratch, keeping its identity and position in the workspace but incrementing its version. Use this when the user rejects an option outright — "I don't like Option B, replace it with something that has less corridor and a bigger living room". The room program carries over from the plan being replaced unless new requirements are supplied, and the engine deliberately picks a different strategy so the geometry visibly changes. Returns the previous and new scores plus the concrete changes.

Input schema

Property	Type	Required	Description
`planId`	string	yes	Id of the target plan, from get_project_state. Also accepts a plan name ("AI Option B"), or "active" for the current working plan. Omit to use the active plan.
`requirements`	object	no	The rooms and features the dwelling must contain.
`priorities`	array	no	Ranked design priorities in the user's own words, e.g. ["space efficiency", "bedroom privacy", "natural daylight", "practical room adjacency"]. The layout engine maps these onto zoning, corridor width and area weighting, and reports back which ones it recognised.
`strategy`	string	no	Optional explicit layout strategy. Leave this out to let the engine choose from the stated priorities. Each strategy produces a genuinely different site organisation and interior zoning, not just a different label.

Raw JSON schema

{
  "type": "object",
  "properties": {
    "planId": {
      "type": "string",
      "description": "Id of the target plan, from get_project_state. Also accepts a plan name (\"AI Option B\"), or \"active\" for the current working plan. Omit to use the active plan."
    },
    "requirements": {
      "type": "object",
      "description": "The rooms and features the dwelling must contain.",
      "properties": {
        "bedrooms": {
          "type": "integer",
          "minimum": 0,
          "maximum": 6,
          "description": "Number of bedrooms. The first is treated as the master and sized larger."
        },
        "bathrooms": {
          "type": "integer",
          "minimum": 0,
          "maximum": 4,
          "description": "Number of bathrooms. Defaults to 2 when three or more bedrooms are requested."
        },
        "maidRoom": {
          "type": "boolean",
          "description": "Include a maid / staff room in the service zone."
        },
        "storageRoom": {
          "type": "boolean",
          "description": "Include a dedicated store room."
        },
        "laundryRoom": {
          "type": "boolean",
          "description": "Include a laundry / utility room, placed next to the kitchen."
        },
        "kitchenType": {
          "type": "string",
          "enum": [
            "closed",
            "open"
          ],
          "description": "\"closed\" gives the kitchen its own door; \"open\" leaves it open to the living/dining space."
        },
        "diningRoom": {
          "type": "boolean",
          "default": true,
          "description": "Include a distinct dining area."
        },
        "garden": {
          "type": "boolean",
          "description": "Allocate garden area on the plot outside the building envelope."
        },
        "parkingSpaces": {
          "type": "integer",
          "minimum": 0,
          "maximum": 4,
          "description": "Number of car parking spaces to allocate on the plot."
        },
        "stairs": {
          "type": "boolean",
          "description": "Place a stair core (for a future upper floor)."
        }
      }
    },
    "priorities": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Ranked design priorities in the user's own words, e.g. [\"space efficiency\", \"bedroom privacy\", \"natural daylight\", \"practical room adjacency\"]. The layout engine maps these onto zoning, corridor width and area weighting, and reports back which ones it recognised."
    },
    "strategy": {
      "type": "string",
      "enum": [
        "balanced",
        "living-first",
        "privacy-first",
        "outdoor-first",
        "storage-first"
      ],
      "description": "Optional explicit layout strategy. Leave this out to let the engine choose from the stated priorities. Each strategy produces a genuinely different site organisation and interior zoning, not just a different label."
    }
  },
  "required": [
    "planId"
  ]
}