Skip to main content
Glama

Remove background

remove_background

Removes the background of a picture (PNG with transparency; from the Дизайн plan, charged in credits). Give job_id of one of your genframe pictures or image_url.

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

Input Schema

NameRequiredDescriptionDefault
job_idNo
image_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations it discloses three useful facts an agent cannot get from structured fields: the return is a PNG with transparency, the feature is gated behind the Дизайн plan, and it consumes credits. It does not say whether the call is synchronous or returns a job to poll, which matters because the input itself is a job_id.

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?

A single front-loaded sentence with the verb and resource first, then the input instructions. The parenthetical bundles three unrelated facts (format, plan, billing), which is dense but still compact with no filler.

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 two-parameter tool with no output schema, it covers purpose, return format, cost, plan gating, and both input sources. The remaining gap is the empty-argument and mutual-exclusivity case, plus sync-versus-async behavior, given both parameters are optional.

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 0%, so the description carries the burden and does add meaning: job_id points to 'one of your genframe pictures' and image_url is an alternative source. However, it never states that the two are mutually exclusive, nor what happens when neither is supplied despite both being non-required.

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 ('Removes the background of a picture') and adds the output characteristics ('PNG with transparency'), which is more than the title alone conveys. It does not explicitly contrast itself with transform siblings such as upscale_image or vectorize, so sibling differentiation is left implicit.

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?

The clause 'Give job_id of one of your genframe pictures or image_url' scopes the acceptable inputs and thereby implies the tool is for images already in the account or reachable by URL. There is no explicit when-to-use versus alternatives, no statement that exactly one input must be supplied, and no guidance on when this is preferable to other image tools.

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