Skip to main content
Glama
pedra-ai

Pedra MCP Server

Official
by pedra-ai

Furnish / virtually stage

pedra_furnish

Upload a room photo to add AI-generated furniture based on selected style and room type. Returns a staged image URL.

Instructions

Virtually stage (furnish) a room with AI-generated furniture. Returns the staged image URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageUrlYesURL (or data: URL) of the source image.
roomTypeNoe.g. "Living room", "Bedroom", "Kitchen". Auto-detected if omitted.
styleNoe.g. "Minimalist", "Scandinavian", "Modern".
creativityNoStrength of the AI transformation. Defaults to "Medium".
Behavior3/5

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

With no annotations, the description carries full burden. It states the return value (staged image URL) but lacks details on safety, reversibility, or API limits. Adequate but minimal.

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?

Single sentence, front-loaded with 'Virtually stage'. Very concise, but sacrifices some behavioral and usage details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 4 parameters and no output schema, the description is only a brief overview. It does not explain parameter interplay (e.g., style vs roomType), leaving the agent with gaps.

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 coverage is 100%, so parameters are well-documented in the schema. The description adds no extra meaning beyond what's already in the input schema.

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?

The description uses specific verbs 'stage/furnish' and resource 'room', clearly stating the tool's function. It distinguishes from siblings like 'pedra_edit_via_prompt' or 'pedra_empty_room' by focusing on furniture addition.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. Siblings include many image editing tools, but the description does not specify conditions or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pedra-ai/pedra-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server