Skip to main content
Glama

Car Background AI

List backgrounds

list_backgrounds
Read-only

List the background scenes available for car photos: built-in studios, showrooms and outdoor settings, plus the workspace's own custom backgrounds (custom: true, made with create_background or in the app). Call this first to pick a scene: each entry has a preview image, an example with a car, and the id that generate_background takes as background_id (custom ones also go to refine_background and delete_background). Read-only and free; takes no parameters and returns every scene in one response. For logos use list_logos 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_backgrounds"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the description's added "Read-only and free" mainly reinforces cost, which is genuinely useful non-schema information. "Takes no parameters and returns every scene in one response" tells the agent there is no pagination or filtering to worry about. It stops short of noting auth/workspace-scoping requirements, which keeps it off a 5.

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?

Three sentences, front-loaded with the core action, then usage sequencing, then the sibling exclusion. Density is high but nearly every clause carries a distinct fact; the parenthetical about `custom: true` and the create_background origin is slightly packed but still earns its place.

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 zero-parameter, read-only listing tool with no output schema, the description covers what it returns, what each entry includes, the field name consumed by downstream tools, and the sibling alternative. 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?

The tool takes zero parameters, so the baseline is 4. The description still adds value by explaining what each returned entry contains (preview image, an example with a car, and the `id`), which compensates for the absence of an output 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 ("List the background scenes available for car photos") and enumerates the scope: built-in studios, showrooms, outdoor settings, plus the workspace's own `custom: true` entries. It also names the sibling it is not ("For logos use list_logos instead"), so an agent can distinguish it without opening any schema.

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?

Explicit sequencing advice ("Call this first to pick a scene") plus downstream routing: the `id` feeds generate_background as `background_id`, and custom ones also go to refine_background and delete_background. It also names the alternative for a different resource type (list_logos), covering when-not-to-use.

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