Skip to main content
Glama
Sign In

Unraster

by ai.unraster
OverviewDiscussionsAdmin

Convert an image

convert_image
Idempotent

Convert a PNG, JPEG or WebP image into an editable PowerPoint (.pptx) and/or SVG and return download links. Spends credits only when files are delivered (SVG 1, PowerPoint 2); a failed conversion is not charged. Waits up to about 45 seconds; if still running, returns conversion_id for get_conversion. Identical requests within 10 minutes reuse the same conversion. The first PowerPoint-only conversion (outputs: pptx) of an account signed up with Google is free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "convert_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
outputsNopptx = editable PowerPoint (2 credits), svg = editable SVG (1 credit), both = 3 credits.pptx
image_urlNoPublic https URL of a PNG, JPEG or WebP image (up to 25 MiB). Private or internal addresses are refused.
mime_typeNoRequired with image_base64.
image_base64NoBase64-encoded PNG, JPEG or WebP bytes (up to 5 MB decoded). Use instead of image_url for local files.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: credit prices per output mode, no charge on failed conversions, the ~45s wait ceiling, the 10-minute dedupe window, and the free first pptx-only conversion. These are exactly the cost, latency and idempotency facts an agent needs before spending a user's credits.

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?

Front-loads what the tool produces, then layers cost, timeout and dedupe behavior in short, information-dense sentences. Every sentence carries operational value, though the parenthetical pricing and free-tier asides make it slightly packed.

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

Completeness5/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 still states what comes back (download links) and what comes back instead when the job runs long (conversion_id). Cost, timing, failure handling and dedupe behavior are all covered for a four-parameter conversion tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3; the description adds real meaning by tying the outputs value 'pptx' to the free-tier condition and by explaining credit charges per mode. It does not add anything for image_url versus image_base64 beyond what the schema already states.

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?

Names a specific verb (Convert) and precise inputs/outputs: PNG, JPEG or WebP into an editable .pptx and/or SVG with download links. It also distinguishes itself from get_conversion by naming it as the follow-up path for long-running jobs.

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?

Gives clear operating context: it waits ~45s and falls back to get_conversion with a conversion_id, and it notes a free first pptx-only conversion for Google sign-ups. It never mentions when to prefer the sibling quote_conversion, which is the one remaining routing gap.

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

All Unraster toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources