Skip to main content
Glama

Image Remove Background Price

image_remove_background_price

Calculate price for image background removal.

Pass the image, or its width and height.


Available models:

  • Ben2: input size=128-2048x128-2048

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 observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It partially meets that by disclosing the available model and its input-size bounds (128-2048 per dimension), which tells the agent an operation's validity constraints at quoting time, but it never says the tool only quotes without performing work, nor anything about pricing units, auth, or error behavior. An output schema exists, which lowers the burden for return values.

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 put the action and the input rule first, followed by a compact model block. The `---` separator and the single-model list are slightly wasteful, but there is no padding or repetition.

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 four-parameter quoting tool with a full schema and an output schema, the description covers the essentials: what it does, the two accepted input modes, and the model constraint that the schema cannot express. The main omission is failing to distinguish this from the actual removal tool, which the agent must infer.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, and the description earns a bump because the `model` parameter has no enum in the schema. The description supplies the only concrete valid value (`Ben2`) plus its 128-2048 input-size limits, which is real meaning the schema does not provide.

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 states a specific verb and resource: 'Calculate price for image background removal.' That clearly separates a quoting tool from the execution sibling image_remove_background, though the description never names the sibling explicitly, so the differentiation is inferred rather than stated.

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?

It gives a concrete usage rule for inputs: 'Pass the image, or its width and height.' That is useful but it is an input convention, not a when-to-use rule. There is no explicit statement about when to call this versus the actual background-removal tool, nor any exclusion or prerequisite.

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.