Skip to main content
Glama

Image Remove Background Price

image_remove_background_price

Calculates the cost of removing an image background before you run the job. Provide an image or its width and height plus a model name to get a price quote.

Instructions

Calculate price for image background removal.

Pass the image, or its width and height.

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": {
      "model": "<model>"
    },
    "name": "image_remove_background_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageNoImage to quote (URL, data URI or base64); its size is read from it
modelYesBackground removal model name
widthNoImage width in pixels (required if image not provided)
heightNoImage height in pixels (required if image not provided)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.3

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. "Calculate price" implies a non-destructive, read-only estimate, which is the key trait, but it says nothing about credit/account requirements, what happens if the image is unreadable, or that no image is actually processed. The output schema covers return values, which limits the gap.

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?

Two short, front-loaded sentences with no filler; the purpose leads and the input modes follow. It is efficient but so terse that nothing else earns a place because nothing else is present.

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 4-parameter tool with full schema coverage and an output schema, the definition is minimally sufficient: purpose plus mutual exclusivity of image vs width/height. It leaves the model choice unexplained and never clarifies the quote-versus-execute relationship with image_remove_background.

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 baseline is 3. The one sentence about the image or width/height echoes the schema's own "required if image not provided" notes and adds no new meaning, and the required model parameter is never discussed.

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?

"Calculate price for image background removal" names a specific verb (calculate price) and resource (image background removal), which distinguishes it from the action sibling image_remove_background. It is clear but does not explicitly say it only quotes and does not execute the removal.

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

Usage Guidelines2/5

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

The description never states when to use this quote tool versus the actual image_remove_background operation, nor any prerequisites or exclusions. "Pass the image, or its width and height" is invocation mechanics rather than when-to-use guidance.

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