Pedra MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Furnish / virtually stage

pedra_furnish

Virtually stage a room with AI-generated furniture and return the staged image URL. Pass a propertyId to save the result into that property's gallery.

Instructions

Virtually stage (furnish) a room with AI-generated furniture. Returns the staged image URL. Pass propertyId to save the result into that property's gallery instead of only returning a URL.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Optional name for the original photo (e.g. its file name), up to 200 characters. Only used with propertyId: if the photo isn't in that property yet, it's saved there under this name in the same call and returned as source.name. A photo already in the property keeps its name. Never shown on the image.
`style`	No	e.g. "Minimalist", "Scandinavian", "Modern".
`imageUrl`	Yes	Source image: a public https:// URL, a data: URI, or an absolute path to a local image file on this computer (the file is read and inlined automatically). If the photo is on the user's device and can't be read from here (e.g. it's on their phone), get a link from pedra_create_upload_link.
`roomType`	No	e.g. "Living room", "Bedroom", "Kitchen". Auto-detected if omitted.
`propertyId`	No	Optional id of the Pedra property (from pedra_list_properties) this photo belongs to. When set, the result is saved into that property's gallery — visible and editable from the app — instead of only being returned as a URL.
`preserveAspectRatio`	No	By default the output comes back at whatever size the AI model produces, which may not match the input's aspect ratio or resolution. Set to true to get the result at the exact width and height of the input image (center-cropped to the original aspect ratio, never stretched). Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.6.0Oct 7, 2026

addedInput schema / properties / name

Added value: +{
+  "description": "Optional name for the original photo (e.g. its file name), up to 200 characters. Only used with propertyId: if the photo isn't in that property yet, it's saved there under this name in the same call and returned as source.name. A photo already in the property keeps its name. Never shown on the image.",
+  "maxLength": 200,
+  "type": "string"
+}

addedInput schema / properties / preserveAspectRatio

Added value: +{
+  "description": "By default the output comes back at whatever size the AI model produces, which may not match the input's aspect ratio or resolution. Set to true to get the result at the exact width and height of the input image (center-cropped to the original aspect ratio, never stretched). Defaults to false.",
+  "type": "boolean"
+}

addedInput schema / properties / propertyId

Added value: +{
+  "description": "Optional id of the Pedra property (from pedra_list_properties) this photo belongs to. When set, the result is saved into that property's gallery — visible and editable from the app — instead of only being returned as a URL.",
+  "type": "string"
+}

Changed2 schema fields changedv0.5.1Oct 4, 2026

removedInput schema / properties / creativity

Removed value: -{
-  "description": "Strength of the AI transformation. Defaults to \"Medium\".",
-  "enum": [
-    "Low",
-    "Medium",
-    "High"
-  ],
-  "type": "string"
-}

changedInput schema / properties / imageUrl / description

Previous value: -"Source image: a public https:// URL, a data: URI, or an absolute path to a local image file (the file is read and inlined automatically)."New value: +"Source image: a public https:// URL, a data: URI, or an absolute path to a local image file on this computer (the file is read and inlined automatically). If the photo is on the user's device and can't be read from here (e.g. it's on their phone), get a link from pedra_create_upload_link."

Changed1 schema field changedv0.1.2Jun 25, 2026

changedInput schema / properties / imageUrl / description

Previous value: -"URL (or data: URL) of the source image."New value: +"Source image: a public https:// URL, a data: URI, or an absolute path to a local image file (the file is read and inlined automatically)."

First observedv0.1.0Jun 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, so safety is partly covered. The description adds real side-effect detail beyond them: the result is saved into the property's gallery 'visible and editable from the app' when propertyId is set, versus only returning a URL otherwise. It does not mention credit cost or latency, which pedra_credits hints are relevant.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero waste, front-loaded with the core action and followed by the single most consequential option. Every clause earns its place.

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 no output schema, the description correctly states the return value (staged image URL) and covers the persistence nuance. For a 6-parameter generative tool, the remaining gap is cost/async expectations, but nothing needed to invoke it correctly is missing.

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 every parameter is already documented with format, defaults, and examples (e.g. preserveAspectRatio's cropping behavior, imageUrl's accepted forms). The description's propertyId sentence restates the schema rather than adding new semantics, so the baseline 3 is correct.

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

Purpose5/5

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

States a specific verb and resource: 'Virtually stage (furnish) a room with AI-generated furniture,' plus the return artifact ('Returns the staged image URL'). It is clearly distinguishable from siblings like pedra_empty_room (the inverse operation) and pedra_renovation.

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?

The description gives one conditional usage rule (pass propertyId to persist into a gallery rather than only getting a URL), which is useful, but offers no guidance on when to choose this over adjacent tools like pedra_renovation, pedra_edit_via_prompt, or pedra_enhance. Usage is implied rather than framed against alternatives.

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

Furnish / virtually stage

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools