Pixly

Floor Plan Render

render_floor_plan

Turn a picture of any floor plan — a hand sketch, a photo of a brochure page, a blueprint, a screenshot — into a polished real-estate floor plan: a furnished top-down 2D plan with real floors and room names, or a 3D isometric cutaway. The rooms, walls, doors and windows are kept exactly as drawn; nothing is added and written dimensions are left off. Costs credits from the user's Pixly balance.

Input Schema

Name	Required	Description
`look`	No	Which picture to make of the plan: 'furnished' (the default — a polished top-down 2D plan with real floors, furniture and room names) or 'isometric' (a 3D cutaway of the same layout, furnished, no text). The photo must show a floor plan: a hand sketch, a brochure page, a blueprint, a screenshot. The layout is kept exactly as drawn; written dimensions are left off.
`r2Path`	No	Storage path of a photo already in the user's Pixly library (from list_library, or returned by an upload ticket) — the alternative to imageUrl.
`imageUrl`	No	Public https URL of the source photo, or a data: URI. Either imageUrl or r2Path is required.
`listingId`	No	A property folder (from list_listings or create_listing) to put the result in. Results of a photo that is already in a folder go there by themselves.

Output Schema

Name	Required	Description
`jobs`	No	Several jobs at once (get_job with jobIds, or a plan's steps): each one's jobId, status and results
`note`	No
`type`	No
`error`	No
`jobId`	Yes	Pass to get_job to poll
`quote`	No	Present when status is "awaiting_confirmation": nothing ran and nothing was charged yet — the price and settings the user is asked to confirm
`status`	Yes	pending \| processing \| completed \| failed — anything not completed/failed is still running
`createdAt`	No
`resultUrls`	No	Present when completed; valid 7 days
`completedAt`	No
`resultPaths`	No	Storage path of each result — pass one as r2Path (or beforeR2Path, a photos[] item) to run another tool on this result
`creditsCharged`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 11, 2026

addedInput schema / properties / listingId

Added value: +{
+  "description": "A property folder (from list_listings or create_listing) to put the result in. Results of a photo that is already in a folder go there by themselves.",
+  "type": "string"
+}

addedOutput schema / properties / jobs

Added value: +{
+  "description": "Several jobs at once (get_job with jobIds, or a plan's steps): each one's jobId, status and results",
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedOct 6, 2026

addedOutput schema / properties / quote

Added value: +{
+  "description": "Present when status is \"awaiting_confirmation\": nothing ran and nothing was charged yet — the price and settings the user is asked to confirm",
+  "type": "object"
+}

Changed1 schema field changedOct 2, 2026

addedOutput schema / properties / resultPaths

Added value: +{
+  "description": "Storage path of each result — pass one as r2Path (or beforeR2Path, a photos[] item) to run another tool on this result",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

AddedSep 23, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations only declare the mutation profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=true). The description adds meaningful behavior beyond that: a preservation guarantee that rooms/walls/doors/windows are kept exactly as drawn, nothing is added, written dimensions are omitted, and that the call consumes Pixly credits. Return/pagination behavior is not described, but an output schema exists to cover that.

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?

Two sentences, front-loaded with the input-to-output transformation before the preservation constraint and cost note. Slightly long and partially duplicative of the schema's look enum text, but no sentence is wasted.

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 an output schema present, return values need not be explained, and all four parameters are covered. The description supplies the important non-obvious context (layout is preserved, dimensions dropped, credits consumed, open-world rendering). Adding explicit sibling routing would complete it.

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 the schema already documents look, r2Path, imageUrl and listingId in detail. The description reinforces the enum's two output styles but adds no syntax or precedence detail beyond the schema (e.g. which of imageUrl/r2Path wins is left to the schema). Baseline 3 is correct when the schema carries the load.

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

Purpose4/5

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

States a specific transformation (a photo of a floor plan 6 a polished furnished 2D or 3D isometric plan) with concrete input examples (hand sketch, brochure photo, blueprint, screenshot). An agent can tell this renders an existing plan photo, which implicitly differs from draw_floor_plan, but the description never names or contrasts that sibling, so differentiation is only inferable.

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

Usage Guidelines3/5

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

Usage context is implied by the input requirements ('a picture of any floor plan'), and the credit cost is stated, but there is no explicit when-to-use vs. when-not, and no routing to the obvious alternative (draw_floor_plan) or to upload paths for sourcing an image.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Pixly tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?