Skip to main content
Glama
pedra-ai

Pedra MCP Server

Official
by pedra-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Replace sky

pedra_sky_blue

Replace a dull or overcast sky in real estate photos with a clear blue one. Optionally save the edited image to a property gallery by passing propertyId.

Instructions

Replace a dull or overcast sky with a clear blue one. Returns the image URL with the new sky. Pass propertyId to save the result into that property's gallery instead of only returning a URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOptional 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.
imageUrlYesSource 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.
skyStyleNoOptional named sky style.
propertyIdNoOptional 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.
preserveAspectRatioNoBy 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.

  1. Changed3 schema fields changedv0.6.0
    • 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"
+}
  2. Changed1 schema field changedv0.5.1
    • 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."
  3. Changed1 schema field changedv0.1.2
    • 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)."
  4. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already mark this as a non-readOnly, non-destructive, open-world operation, so the safety profile is covered. The description adds real behavioral value beyond that: it discloses the return value ('image URL with the new sky') and the side effect of propertyId saving the result into a gallery rather than only returning a URL. It does not mention credit consumption or processing time, which keeps it short of a 5.

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 padding, and the core purpose is front-loaded before the return-value and persistence details. Every clause carries information the agent needs.

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 what is returned, and the rich input schema covers parameters and input guidance. For a mutation tool it is nearly complete, though it could mention credit cost (pedra_credits is a sibling) and that skyStyle values are constrained.

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 every parameter in detail. The description's note about propertyId saving to the gallery largely restates what the propertyId schema description already says, so it adds little beyond the structured fields — the baseline 3 for full coverage applies.

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 states a concrete verb and resource: replace a dull/overcast sky with a clear blue one. This is unambiguous and clearly distinguishable from siblings such as pedra_enhance, pedra_furnish, or pedra_edit_via_prompt, since it names a specific transformation target (the sky).

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?

It implies the triggering condition ('dull or overcast sky') but never states when to choose this over alternatives like pedra_edit_via_prompt or pedra_enhance, nor any exclusions (e.g. indoor shots, already-blue skies). Usage is inferable but never explicit.

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

Deploy Server

Other Tools