Skip to main content
Glama

Car Background AI

Hide license plates

hide_license_plates

Hide the license plates in a car photo without changing anything else, for privacy before publishing a listing. Use this when the background should stay as it is; when the background is being replaced as well, set hide_license_plate on generate_background instead of calling both. style chooses a blur (default) or a solid block, and block_color sets the block's colour. Uses no credits: it is included with an active subscription, up to a fair-use monthly limit, and returns subscription_required for a workspace without one. The source photo is not modified; the result is returned as an image, with the areas that were hidden listed as plates.

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

Input Schema

NameRequiredDescriptionDefault
styleNoBlur the plate (default) or cover it with a block.
image_urlYesPublic HTTPS URL of the car photo (JPEG, PNG or WebP).
block_colorNoHex colour of the block, e.g. #FFFFFF. Default black.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), the description discloses credit cost (none, subscription-included), a fair-use monthly limit, and the `subscription_required` failure mode for workspaces without a plan. It also states the source photo is not modified and describes the return payload (image plus a `plates` list of hidden areas), which the missing output schema would otherwise leave unknown.

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 purpose is front-loaded in the first clause, followed by the exclusion rule, the parameter note, and cost/return behavior in a logical order. It is dense but every clause carries information; only the `style`/`block_color` restatement is close to redundant with the schema.

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?

For a three-parameter image tool with no output schema, the description covers the exclusion path, the default styling, the subscription/billing model, the error case, non-destructiveness of the source, and the return shape. Nothing an agent needs in order to call it correctly or interpret the failure appears to be missing.

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 schema already documents `style`, `image_url`, and `block_color`, including the blur default. The description restates the blur-default and block-color behavior without adding format or edge-case detail, so it matches the baseline for a fully documented schema.

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?

The description uses a specific verb and resource ('Hide the license plates in a car photo') and scopes the effect ('without changing anything else, for privacy before publishing a listing'). It also distinguishes the tool from the sibling that subsumes it, saying to set `hide_license_plate` on generate_background rather than calling both.

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?

It gives an explicit when-to-use condition ('when the background should stay as it is') and the explicit when-not case ('when the background is being replaced as well'), naming the alternative tool and the specific parameter to use instead. No inference is required from the agent.

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