Skip to main content
Glama

Car Background AI

List logos

list_logos
Read-only

List the logos stored for the workspace, to get the id that other tools need. type selects which set is returned: logo (default) for dealer logos drawn on finished photos, passed as logo.id to generate_background, or plate for designs shown on the license plate, passed as license_plate_logo.id. Each entry has id, type, image_url and created_at. Also call it before delete_logo, or before upload_logo to see whether the logo is already stored. Read-only and free. For background scenes use list_backgrounds instead.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_logos"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description reinforces it and adds the cost signal ('free'). It also discloses the return shape (id, type, image_url, created_at), which matters because no output schema exists. Only minor gap: no mention of ordering or volume of results.

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-loaded with purpose, then type semantics, then return fields, then use cases, then the sibling redirect. Every clause carries information (no restatement of the title), and it stays compact despite covering five distinct points.

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 single-optional-param read tool with no output schema, the description supplies the return fields, the id-chaining contract with generate_background, and the pre-delete/pre-upload checks. Nothing an agent needs in order to call it correctly is missing.

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% and the enum values are already documented, so the baseline is 3; the description goes further by explaining downstream wiring — `logo` entries feed `logo.id` in generate_background, `plate` entries feed `license_plate_logo.id`. That adds meaning the schema cannot express.

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 ('List the logos stored for the workspace') and immediately frames the goal: obtaining the `id` other tools need. It explicitly separates itself from list_backgrounds and explains the two logo sets, so an agent can pick it confidently.

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 conditions: before delete_logo, before upload_logo to check for duplicates, and explicitly redirects to list_backgrounds for background scenes. Both the alternative and the condition selecting it 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