Create floorplan
create_floorplanCreate a floorplan row. Provide EXACTLY ONE of building_id (per-building floor) or site_id (site-level / campus plan). Typically the web app calls this per page of an uploaded PDF; MCP clients rarely need to call this directly since they do not upload the PDF itself. Requires floorplans:write scope.
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": {
"floor_label": "<floor_label>",
"pdf_storage_path": "<pdf_storage_path>",
"pdf_filename": "<pdf_filename>"
},
"name": "create_floorplan"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| status | No | Detection status (default: pending) | |
| site_id | No | Site this plan belongs to (use for site-level / campus plans; omit if building-scoped) - resolve via list_sites | |
| building_id | No | Building this floor belongs to (omit if site-scoped) - resolve via list_buildings | |
| floor_label | Yes | Human-readable label (e.g. "Ground Floor", "Mezzanine", "Site Plan") | |
| floor_order | No | Sort order within the scope (lowest first) | |
| page_number | No | 1-indexed page number within the PDF | |
| pdf_filename | Yes | Original filename for display | |
| page_width_pt | No | Page width in PDF points (discovered client-side) | |
| page_height_pt | No | Page height in PDF points | |
| pdf_storage_path | Yes | Supabase Storage path to the PDF file |