Skip to main content
Glama

Car Background AI

Delete logo

delete_logo
Destructive

Permanently delete one of the workspace's stored logos, e.g. an outdated logo or to free one of the seven slots before upload_logo. It cannot be undone through this server; the logo has to be uploaded again to restore it. Photos already generated keep the logo they were made with, and later generate_background calls can no longer use this id. Get the id from list_logos, and pass the same type the logo was listed under (logo by default, or plate). Free. Returns the id with deleted: true, or not_found when the id is unknown for that type.

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": {
      "id": "<id>"
    },
    "name": "delete_logo"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesA logo `id` from list_logos.
typeNo`logo` (default): logos drawn on finished photos. `plate`: designs put on the license plate.

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?

Beyond the destructiveHint=true/readOnlyHint=false annotations, it discloses that deletion is irreversible through the server, that already-generated photos retain the old logo, and that future generate_background calls can no longer reference the id — real side-effect information the annotations cannot express. It also states cost ('Free') and the exact return payload including the not_found case.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the action and its permanence, then layers prerequisites, side effects, and return value in a tight sequence. No sentence is filler — even the 'Free' note and the return-shape sentence carry information an agent needs and that no structured field supplies.

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?

With no output schema, the description compensates by spelling out the return shape (id with deleted: true, or not_found). For a two-parameter destructive tool it covers prerequisites, side effects, recovery, and failure modes fully.

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 is 3; the description adds a cross-parameter constraint the schema does not: pass the same `type` the logo was listed under, defaulting to `logo`. That is useful operational meaning beyond the enum, though the plate/logo semantics themselves are already in the 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?

States a specific verb and resource ('Permanently delete one of the workspace's stored logos') plus the slot constraint (one of seven). It is immediately distinguishable from list_logos (which supplies the id) and upload_logo (which consumes the freed slot).

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?

Gives concrete when-to-use triggers ('an outdated logo or to free one of the seven slots before upload_logo') and points to list_logos as the prerequisite source of the id. It also warns that the only recovery path is re-uploading, which tells the agent when caution is warranted.

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