Conecto

Resize or convert an image

image_transform

A new image from one in the file store: resized (fit inside the box, or cover it and crop the overflow from the center), converted to WebP, AVIF, JPEG or PNG, and compressed. Photos come out turned the right way up with their metadata (GPS included) removed. Costs $0.005 per call; nothing if it fails.

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": {
      "file_id": "<file_id>"
    },
    "name": "image_transform"
  }
}

Input Schema

Name	Required	Description	Default
`fit`	No		inside
`name`	No
`width`	No
`format`	No		webp
`height`	No
`file_id`	Yes	An image in the file store.
`quality`	No
`link_hours`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Adds real context the annotations do not: exact cost ($0.005 per call, nothing on failure), automatic EXIF rotation, and removal of all metadata including GPS. Annotations only say readOnly=false, destructive=false, idempotent=false. What it does not disclose is where the new image lands and how the caller retrieves it.

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?

Tight and front-loaded: the transformation is stated first, then the corrective/metadata behavior, then the price. Only minor redundancy in restating the format list already present in the schema enum.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter mutation with no output schema, the definition should say what is produced and how it is addressed (the presence of link_hours hints at a temporary download link, which is never mentioned). The cost and metadata behavior are strong, but the output contract is missing.

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 13%, so the description must compensate, and it partly does: it explains the 'inside' vs 'cover-and-crop-from-center' semantics of the fit enum and names the four output formats, which goes beyond the bare enum lists. However width, height, name, quality (only implied by 'compressed'), and especially link_hours are never explained, leaving the most consequential parameter undocumented.

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 (produce a new image from one in the file store) and enumerates the exact operations: resize, convert to WebP/AVIF/JPEG/PNG, compress. It is easy to distinguish from the only close sibling, image_info, and the summary sentence carries the full transformation semantics.

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?

Usage is implied by the input (an image already in the file store) but there is no explicit when-to-use guidance, no mention of alternatives such as image_info, and no prerequisites or limits beyond the price. The reader must infer that no source URL/resize-on-upload path exists.

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

All Conecto tools Inspect

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

Need Help?