Skip to main content
Glama

Kubeez

remove_background

PRE-FETCH (mandatory): resources/read kubeez://skills/media-upload AND kubeez://skills/billing-confirmation.

Cut the subject out of an image. The output is a PNG with a REAL transparent background (alpha) — use this instead of prompting an image model for a 'transparent background', which bakes a white or checkerboard fill into the pixels. Ideal for logos, product shots, mascots, and cutouts you will composite over something else.

Scope: generate:media. Billing: flat per image — call estimate(model='remove-background') for the exact price, tell the user, and get confirmation before calling this. Takes NO prompt: it is an operation on an existing image, not a generate_media model.

CANONICAL FLOW: (1) if the user has a local file, call get_upload_url(model_id='remove-background') and send them the link. (2) when they confirm the upload, call get_upload_session(token) to get the public URL. (3) quote the price and ask for confirmation. (4) ONLY THEN call this tool.

Required: image_url — a public HTTPS URL of a .jpg / .jpeg / .png / .webp image (max 5MB; the provider rejects other formats). An already-generated Kubeez image works directly — pass its output URL.

Async: returns {generation_id, status: 'pending'} immediately. Poll get_status(generation_id) until status is 'completed'; the output URL is the cutout PNG. Also available in-app at kubeez.com (image tools → Background Remover).

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

Input Schema

NameRequiredDescriptionDefault
image_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false; the description goes well beyond by disclosing the flat per-image billing model, the required scope generate:media, and the mandatory user confirmation step. It also discloses the asynchronous contract (returns {generation_id, status: 'pending'} and must be polled via get_status) and provider-side validation limits.

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?

Long for a one-parameter tool, but structured with labeled sections (PRE-FETCH, Scope, Billing, CANONICAL FLOW, Required, Async) and front-loaded with the mandatory prerequisite and the core action. The trailing in-app pointer at kubeez.com is the one line that does not earn its place.

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

Completeness5/5

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

Covers everything an agent needs for a billed, async generation tool with a single undocumented parameter: prerequisites, cost/confirmation gate, valid input formats and size ceiling, upload workflow, and the polling path to retrieve the result. The output schema exists, yet the async return shape is still accurately described.

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

Parameters5/5

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

Schema coverage is 0%, so the description must compensate and does: image_url is a public HTTPS URL of a .jpg/.jpeg/.png/.webp image, max 5MB, with other formats rejected by the provider. It also clarifies that an existing Kubeez output URL can be passed directly, and that the tool takes no prompt.

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?

States a specific operation on a specific resource ('Cut the subject out of an image') and defines the output precisely ('PNG with a REAL transparent background (alpha)'). It explicitly contrasts itself with prompting an image model for a transparent background, so an agent can distinguish it from generate_media without opening a schema.

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

Usage Guidelines5/5

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

Names the fit cases (logos, product shots, mascots, composites) and the anti-pattern (don't prompt an image model for 'transparent background'). It also gives an explicit CANONICAL FLOW routing through get_upload_url, get_upload_session, estimate, and get_status, including the confirmation gate before invoking this tool.

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