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

generate_floorplan_variations

act imperative

Produce one to three genuinely different alternative layouts from a base plan, each solved with a different zoning strategy (living-first, privacy-first, outdoor-first, storage-first or balanced) and steered by the given priorities. The geometry really differs — building footprint, garden position, room sizes and circulation all change — so the variations are worth comparing rather than being relabelled copies. Use this when the user asks for "another option" or "a variation with a bigger living room and more bedroom privacy". Variations are appended below the existing plans by default.

Input schema

Property	Type	Required	Description
`basePlanId`	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.
`count`	integer	no	How many variations to generate (1-3).
`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.
`outputMode`	string	no	"append" adds a new plan below the existing ones so the human can compare before and after — this is the recommended default. "replace" overwrites the target plan in place and increments its version.

Raw JSON schema

{
  "type": "object",
  "properties": {
    "basePlanId": {
      "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."
    },
    "count": {
      "type": "integer",
      "minimum": 1,
      "maximum": 3,
      "default": 1,
      "description": "How many variations to generate (1-3)."
    },
    "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."
    },
    "outputMode": {
      "type": "string",
      "enum": [
        "append",
        "replace"
      ],
      "default": "append",
      "description": "\"append\" adds a new plan below the existing ones so the human can compare before and after — this is the recommended default. \"replace\" overwrites the target plan in place and increments its version."
    }
  },
  "required": [
    "basePlanId"
  ]
}