Skip to main content
Glama
pedra-ai

Pedra MCP Server

Official
by pedra-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Enhance image

pedra_enhance

Enhance real-estate photos by improving lighting, color, and sharpness. Returns an image URL, or saves the result to a property gallery when propertyId is provided.

Instructions

Enhance a real-estate photo: improve lighting, color, and sharpness. Returns the enhanced image URL. 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.
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.
preserveOriginalFramingNoPreserve the original framing/aspect ratio/resolution exactly (for verification verticals where the output must legally represent the captured photo). 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

A3.5/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-destructive, open-world operation, and the description usefully adds the return value (enhanced image URL) and the important side effect that passing propertyId persists the result into a property gallery — a meaningful behavioral detail not derivable from the annotations. It omits cost/credit consumption, which matters given the pedra_credits sibling.

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?

Three short sentences with no filler, front-loading the core action before the return-value and propertyId notes. Size is well matched to a single-purpose image tool, though the propertyId sentence is largely a paraphrase of the schema field.

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?

For a 5-parameter tool with full schema coverage, no output schema, and safety annotations already present, the description covers the action, the return, and the persistence option adequately; an agent could call it correctly. Missing only operational context such as cost and expected processing time.

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% and the per-parameter docs are unusually detailed, so the schema does the heavy lifting. The description only restates the propertyId behavior ('save the result into that property's gallery instead of only returning a URL'), adding no syntax or format information beyond it; baseline 3 applies.

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?

Names a specific verb and resource (enhance a real-estate photo) and enumerates the effect (lighting, color, sharpness), which is more than a restatement of the name. It does not, however, distinguish itself from the very close sibling pedra_enhance_and_correct_perspective, so an agent cannot tell from this text alone which of the two to pick.

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 states what happens when propertyId is passed, but never states when to use this tool rather than a sibling (e.g. pedra_enhance_and_correct_perspective when perspective also needs fixing, or pedra_edit_via_prompt for arbitrary edits). No exclusions, no prerequisites, no stated ceiling on what 'enhance' covers.

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