Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

Background Remover

BackgroundRemover
Read-only

Background Remover: Background Remover is an image background removal API. Upload a photo or send its URL and it returns a PNG with the background made transparent, or replaced with a solid color you choose. (Cost: 40 credits)

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": "BackgroundRemover"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPublic URL of the image to process (JPG, PNG, GIF, WebP, BMP supported, max 10MB)
imageNoImage file upload (JPG, PNG, GIF, WebP, BMP supported, max 10MB)
bgColorNoOptional hex color to fill the background with (e.g. #ffffff). Omit for a transparent background.

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message, null on success
statusNo"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already establish that the operation is read-only, open-world, and non-destructive. The description adds useful behavioral context beyond that: the cost of 40 credits and the returned artifact being a PNG with either a transparent background or a chosen solid color.

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?

The definition is a compact, front-loaded paragraph that immediately covers inputs, output, and cost. It has minor redundancy from repeating the tool name and title-like prefix, but no sentence is seriously wasteful.

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 simple image-processing tool with a complete input schema, annotations, and an output schema, the description is largely complete. It covers input modes, output format, background replacement behavior, and cost, though it could clarify URL-vs-upload preference or error behavior.

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%, so the schema already documents url, image, and bgColor in detail. The description restates the upload/URL and background color concepts but adds no extra semantics such as precedence when both url and image are provided.

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 states a specific verb and resource: an image background removal API that accepts a photo or URL and returns a PNG with a transparent or solid-color background. This distinguishes it from generic image conversion or editing tools in the sibling list.

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?

It clearly explains how to invoke the tool by uploading a photo or sending a URL, and notes the credit cost. However, it does not explicitly compare when to use this over nearby image tools such as ImageConverter or HEICConverter, nor does it state when-not to use it.

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

All APIVerve 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