ToolForte

Convert image

image_convert

Convert an image (public URL, max 15MB) to another format (png, jpeg, bmp, gif, tiff), pixels unchanged. Returns a hosted download URL valid for 24 hours. Free demo: 3 renders/day. With a free ToolForte API key (Authorization: Bearer tf_..., get one at https://toolforte.com/developers), which spends your monthly unit balance: 25 units per render.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	Public URL of the source image
`format`	Yes	Target image format

Output Schema

TableJSON Schema

Name	Required	Description
`url`	No	Hosted download URL of the produced file
`bytes`	No	Size in bytes
`result`	No	The result, when it is not an object
`metering`	No	What this call cost and what allowance remains
`expiresAt`	No	When the download URL stops working (ISO 8601)
`contentType`	No	MIME type of the produced file

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedSep 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "bytes": {
+      "description": "Size in bytes",
+      "type": "number"
+    },
+    "contentType": {
+      "description": "MIME type of the produced file",
+      "type": "string"
+    },
+    "expiresAt": {
+      "description": "When the download URL stops working (ISO 8601)",
+      "type": "string"
+    },
+    "metering": {
+      "additionalProperties": {},
+      "description": "What this call cost and what allowance remains",
+      "properties": {
+        "remaining": {
+          "type": "number"
+        },
+        "source": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "result": {
+      "description": "The result, when it is not an object"
+    },
+    "url": {
+      "description": "Hosted download URL of the produced file",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedSep 4, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the 15MB input cap, 24-hour hosted download URL validity, free demo quota of 3 renders/day, API key authentication format, and 25-unit cost per render. No contradiction with readOnlyHint=false, openWorldHint=true, or other annotations.

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 focused sentences with no filler. Each sentence delivers essential operational information: input scope and output behavior, download URL lifetime, and quota/auth/cost details.

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?

For a two-parameter conversion tool with an output schema and annotations, the description covers inputs, constraints, output URL behavior, rate limits, authentication, and pricing. Nothing essential is missing for correct selection and invocation.

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 already covers both parameters with descriptions and an enum for format. The description adds valuable URL-specific constraints ('public URL, max 15MB') and reinforces the target format list, enriching the parameter meaning beyond the schema alone.

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?

States a specific verb and resource: converting an image to another format, names the five supported target formats, and adds the scope constraint 'pixels unchanged'. This clearly distinguishes it from sibling tools like image_resize and image_compress.

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?

Provides clear context: use for format conversion of a public image URL with pixel preservation. It does not explicitly name alternatives or give when-not-to-use instructions, but the 'pixels unchanged' phrase implicitly excludes resizing and compression use cases.

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

All ToolForte tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation4/5

Most tools target a clearly distinct resource and action, so an agent can usually tell them apart. A few close pairs exist (generate_test_bsn vs generate_brp_test_data, html_to_pdf vs url_to_pdf, read_page vs url_screenshot), but the descriptions draw clear boundaries.

Naming Consistency4/5

Tool names consistently use snake_case and mostly follow a verb_noun pattern like generate_slug, validate_email, or pdf_merge. There are a few noun-style exceptions such as base64, csv_to_json, and password_strength, but no mixed casing or chaotic naming.

Tool Count3/5

40 tools is heavy and exceeds the comfortable selection range for most agents. The server presents itself as a general-purpose utility toolbox, so the breadth is defensible, but the large flat tool list creates real navigation burden.

Completeness4/5

The toolkit covers common encoding, conversion, image/PDF, validation, Dutch-specific test data, memory, and workflow needs quite well. Minor gaps like PDF text extraction or JSON-to-CSV conversion exist, but agents can typically work around them.

Resources

Need Help?