Skip to main content
Glama
Pedra MCP Server

Pedra MCP Server

Official
by pedra-ai

Make HD

pedra_make_hd

Upscale photos with AI into sharper, higher-resolution HD images, ideal for small or blurry listing photos. Pass a property ID to save the result to that property's gallery.

Instructions

Upscale a photo with AI to a sharper, higher-resolution version. Use it on small or blurry listing photos. Returns the HD image URL. Pass propertyId to save the result into that property's gallery instead of only returning a URL.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "imageUrl": "<imageUrl>"
    },
    "name": "pedra_make_hd"
  }
}

Input 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A4/5.0
Behavior4/5

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

The annotations only declare readOnly=false, destructive=false, openWorld=true, so the description earns credit for disclosing the side effect that passing propertyId persists the result into the property's gallery and that the tool otherwise just returns a URL. It does not mention credit consumption or processing time, which matters for an AI generation tool given the existence of pedra_credits.

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?

Three short sentences: what it does, when to use it, what it returns, and the optional persistence mode. Nothing is padded and the core action is front-loaded.

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 three-parameter, non-destructive transformation tool with a fully documented schema and declared safety annotations, the description covers purpose, trigger, return value, and the persistence variant. The only real omission is cost/credit and latency expectations, which is a moderate gap rather than a blocking one.

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 all three parameters are already documented in detail, including the propertyId gallery-saving semantics and the name parameter. The description restates the propertyId behavior as a headline, which aids decision-making but adds no syntax or format detail beyond the schema; 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?

The description gives a specific verb and resource ('Upscale a photo with AI to a sharper, higher-resolution version') and states the output ('Returns the HD image URL'). It does not distinguish itself from likely-overlapping siblings such as pedra_enhance or pedra_enhance_and_correct_perspective, so an agent cannot tell purely from this text which upscaling path 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 Guidelines4/5

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

'Use it on small or blurry listing photos' supplies a clear trigger condition for when to reach for this tool. It stops short of naming alternatives or stating when not to use it (e.g., versus pedra_enhance), which keeps it below a 5.

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