Voidless

upload_image

Add an image the user already has to their library, so it can be animated, rotated or edited. The editors work on squares of 32, 48, 64, 96, 128, 192, 256 or 384, 512, 768 or 1024 px; any other picture is centred on the smallest of those that holds it, with transparent padding (scaled down to 1024 if larger), and the reply says so. Give it as a public URL (best: a long base64 string is easy to garble) or as base64. 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": "upload_image"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No	Public http(s) link to the image. Use this when the image is online
`type`	No		character
`image`	No	Base64 image instead of url (a data: prefix is stripped automatically)
`remove_bg`	No	Remove the background on upload

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare this is a non-destructive, non-idempotent, closed-world write, so the bar is lower. The description still adds genuine behavior: non-conforming images are centred on the smallest of a fixed set of square sizes with transparent padding, oversized images are scaled to 1024, and the reply reports this. Cost ('Free') is also disclosed.

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?

Purpose is front-loaded in the first clause, and the size/padding detail follows in one compact sentence. The enumerated size list is verbose but each value is functionally necessary; only minor tightening would improve it.

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 four-parameter upload tool with no output schema, the description covers the consequential unknowns: accepted sizing, padding behavior, the 1024 downscale, input format preference, and the fact that the response acknowledges adjustments. Remaining gaps ('type' semantics, duplicate handling) are minor.

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 coverage is 75%, and the description adds real meaning for the url/image pair, including the strong preference for a public URL and the note that a data: prefix is stripped. It says nothing about the 'type' enum values or 'remove_bg', which are the remaining semantic gaps, so it lands at the baseline for high-coverage schemas.

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?

States a specific verb and resource ('Add an image the user already has to their library') and adds the downstream intent ('so it can be animated, rotated or edited'). The phrase 'the user already has' implicitly separates it from generate_image, but no sibling is named explicitly, so the differentiation is left to inference.

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 rather than stated: bring an image you already possess instead of generating one, and prefer a public URL over base64. There is no explicit 'use generate_image when...' routing and no prerequisites or exclusions, so the agent must infer the alternative from the wording.

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

All Voidless 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?