DropBG AI Background Remover
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| remove_background_fileA | Remove the background from a local image file (PNG, JPG, JPEG, WEBP) using DropBG and save the transparent PNG or solid-color cutout to disk. |
| remove_background_urlA | Remove the background from a public HTTP/HTTPS image URL using DropBG and save the result to a local file path. |
| remove_background_batchA | Remove backgrounds from multiple local image files sequentially (up to 10 files per batch) and save the cutouts to disk. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool is distinguished cleanly by its input source: a single local file, a public URL, or a batch of multiple local files. There is minor conceptual overlap between remove_background_file and remove_background_batch, but the descriptions make the boundary explicit (single vs. up to 10 files).
All three tools follow a uniform remove_background_<target> pattern in snake_case with a consistent verb phrase. The suffix (_file, _url, _batch) maps predictably to the input mode.
Three tools is exactly the right scope for a single-function background-removal service, with one tool per meaningful input channel. Nothing feels padded or missing at the API-shape level.
The surface covers the realistic input paths (file, URL, batch) and a consistent save-to-disk output model, so no dead ends for the core workflow. Minor gap: no tool to return or preview the result inline, and batch is capped at 10 with no job-status/polling tool for larger workloads.