Skip to main content
Glama
pedra-ai

Pedra MCP Server

Official
by pedra-ai

Renovate space

pedra_renovation

AI-powered room renovation: modify walls, floors, finishes, and add or remove furniture, returning the updated image URL.

Instructions

Renovate a space (walls, floors, finishes), optionally furnished. Returns the renovated image URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageUrlYesURL (or data: URL) of the source image.
styleNoRenovation style.
creativityNoStrength of the AI transformation. Defaults to "Medium".
furnishNoWhether the renovated room should be furnished (true → with furniture, false → empty).
roomTypeNoRoom type. Auto-detected if omitted.
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It mentions the output (URL) and optional furnishing, but does not address potential changes, limitations, or whether the operation is destructive. Important behavioral context is missing.

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?

The description is two sentences, front-loading the action and output. Every word serves a purpose with no redundancy.

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?

Given the medium complexity (5 parameters, no output schema, no annotations), the description adequately covers the core purpose and output. However, it could briefly explain the style or creativity parameters to aid selection.

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 already well-documented. The description adds no additional meaning beyond noting the optional furnishing. It meets the baseline but does not compensate for any gaps.

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 the verb 'Renovate' and the resource 'space', listing specific aspects (walls, floors, finishes) and the optional furnishing. However, it does not explicitly distinguish from sibling tools like pedra_furnish or pedra_empty_room, which could cause confusion.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., pedra_furnish for furnishing only, pedra_enhance for enhancements). There are no exclusions or context for appropriate use.

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