Skip to main content
Glama

Car Background AI

Upload logo

upload_logo

Store a logo for the workspace so it can be put on photos later. It does not change any photo by itself: pass the returned id to generate_background as logo.id, or as license_plate_logo.id for a plate logo. The file is fetched from image_url once and a copy is kept (PNG, WebP or JPEG up to 5 MB; a transparent background works best). type is logo (default) for dealer logos or plate for license plate designs, where background sets the plate colour behind a transparent logo. Up to seven per type: when full, remove one with delete_logo first. Check list_logos before uploading to avoid duplicates. Free. Returns the stored logo with its id.

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

Input Schema

NameRequiredDescriptionDefault
typeNo`logo` (default): logos drawn on finished photos. `plate`: designs put on the license plate.
image_urlYesPublic HTTPS URL of the logo.
backgroundNoPlate logos only: hex colour behind a transparent logo. Default white.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (which only say this is a non-destructive, open-world write), the description discloses that the file is fetched once from image_url and a copy is retained, the accepted formats and 5 MB size ceiling, the transparent-background recommendation, the seven-per-type quota, the free pricing, and the return value. These are the operational facts an agent needs before invoking a mutating tool.

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?

Purpose is front-loaded in the first sentence, followed by the 'does not change any photo' clarification and then the workflow constraints. It is a dense single block that mixes parameter notes with quota and format rules, which slightly hinders scanning, but no sentence is filler.

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 upload tool with annotations and no output schema, the description covers the mutation's side effects, prerequisites, limits, and the shape of the return value ('the stored logo with its `id`'). An agent can invoke it correctly without further context.

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, but the description adds meaning the schema does not: the `type` choice determines which downstream id field to use and which quota bucket is consumed, and `background` is framed as the colour behind a transparent plate logo. It stops short of adding format syntax beyond the schema's hex-colour note.

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 opens with a specific verb and resource: 'Store a logo for the workspace,' and immediately scopes it as a prerequisite rather than a photo mutation. It is clearly distinguishable from generate_background (which consumes the logo) and from list_logos/delete_logo (which manage the same collection).

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 states the downstream usage path explicitly ('pass the returned `id` to generate_background as `logo.id`, or as `license_plate_logo.id` for a `plate` logo'), tells the agent to call list_logos first to avoid duplicates, and tells it to call delete_logo first when the seven-per-type cap is hit. Both alternatives and their triggering conditions are named.

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