Skip to main content
Glama
pedra-ai

Pedra MCP Server

Official

Furnish / virtually stage

pedra_furnish

Virtually stage a room with AI-generated furniture. Provide a photo and get a staged image URL with chosen room type and style.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
styleNoe.g. "Minimalist", "Scandinavian", "Modern".
imageUrlYesSource image: a public https:// URL, a data: URI, or an absolute path to a local image file (the file is read and inlined automatically).
roomTypeNoe.g. "Living room", "Bedroom", "Kitchen". Auto-detected if omitted.
creativityNoStrength of the AI transformation. Defaults to "Medium".
Behavior3/5

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

The description notes AI generation, aligning with openWorldHint=true. It does not contradict annotations, but lacks details on what happens to the original image, auth needs, or rate limits.

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 brief sentences, no fluff, front-loaded with action and output.

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

Completeness3/5

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

Covers basic action and return type. Missing guidance on optional parameters, expected output resolution, or processing time. Adequate but not thorough.

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 the schema already describes all parameters. The description adds no extra meaning beyond the schema.

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?

The description clearly states it virtually stages a room with AI-generated furniture and returns the staged image URL. It distinguishes the tool from siblings like pedra_empty_room, but does not explicitly name alternatives.

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 like pedra_empty_room or pedra_renovation. No exclusions or prerequisites mentioned.

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