Skip to main content
Glama

PhotoSweat Background Removal

Remove background

remove_background

Cut out the subject onto transparency, white, or any solid color. Returns the processed image at the same pixel size as the input. $0.01 per image; anonymous is free for 10/day per IP.

Input Schema

NameRequiredDescriptionDefault
colorNoOnly used when background=color#ffffff
formatNoJPEG is much smaller for opaque backgrounds; transparency requires PNGpng
image_urlNoPublic http(s) URL of the image to process (JPEG/PNG/WebP, max 10 MB). Use a hostname, not an IP literal.
backgroundNoTransparent, white, or a custom colortransparent
image_base64NoThe image itself, base64-encoded (JPEG/PNG/WebP, max 10 MB). A data: URI prefix is accepted. Provide either this or image_url.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses the output pixel dimensions ('same pixel size as the input'), the per-image cost ($0.01), and the anonymous rate limit (10/day per IP). It stops short of stating the response encoding (base64 vs URL) or failure behavior (e.g., no subject detected), which are the main remaining gaps for a paid image operation.

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?

Two compact sentences, front-loaded with the operation and output guarantee, then cost and limits. Every clause carries information an agent can act on; nothing is padding.

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 5-parameter tool with a fully documented schema and no output schema, the description covers purpose, output sizing, and cost/limits well. The notable omission is the return transport (base64 payload vs URL) and any error semantics, which matter since there is no output schema to fall back on.

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%, with enums documented for background and format and explicit notes on color and the base64/URL mutual exclusion, so the schema does the heavy lifting. The description adds only the high-level list of background modes, which restates the schema rather than extending it. Baseline 3 applies.

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?

The description opens with a specific verb+resource+outcome: 'Cut out the subject onto transparency, white, or any solid color.' An agent immediately knows this is a background-removal/image-segmentation tool and what the possible outputs are, with no ambiguity about the operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no alternatives are referenced (none exist as siblings, but nothing states prerequisites either). The pricing and free-tier line is cost context rather than usage routing, so an agent gets no explicit decision criteria beyond the tool's obvious name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources