Skip to main content
Glama
Venice MCP Server

Venice MCP Server

Official
by veniceai

Venice Image Background Remove

venice_image_remove_bg

Remove an image background and return a transparent PNG (base64) from a supplied image URL, using x402 wallet or API key authentication.

Instructions

Remove image background; returns a transparent PNG (base64). Supports x402 wallet auth (no Venice account needed) and API key.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "image_url": "<image_url>"
    },
    "name": "venice_image_remove_bg"
  }
}

Input Schema

NameRequiredDescriptionDefault
image_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare the safety profile (not read-only, open-world, not idempotent, non-destructive), and the description adds genuinely new facts: the return is a transparent PNG in base64, and either x402 wallet auth or an API key works. It does not disclose cost, size limits, or processing behavior, so it adds moderate value over the annotations.

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 description is one front-loaded sentence that pairs the action and the output, with the auth detail trailing. Efficient, though the semicolon clause is a compact list, and it could carry one more constraint without bloat.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter tool, the description covers purpose, output format, and auth, which is what annotations and schema don't supply. It still leaves input constraints and the cost or side-effect of the paid call unstated, which matters for a non-read-only, open-world operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single parameter, so the description has to explain image_url, and it doesn't: nothing about accepted formats, whether the URL must be publicly reachable, or size or type limits. The agent can guess the parameter means 'image to process,' but the description compensates for none of the coverage gap.

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?

The description has a specific verb and resource ("Remove image background") and states the output, which cleanly separates it from generate/edit/upscale siblings. It doesn't explicitly name the sibling it contrasts with, but the operation name is unambiguous.

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 only implied by the operation name; there is no explicit when-to-use or when-not-to-use guidance versus venice_image_edit or venice_image_multi_edit. The auth note (x402 wallet or API key) gives useful framing but is not selection guidance.

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