Skip to main content
Glama

generate_theme_from_image

Read-onlyIdempotent

Generate a complete Material Design 3 theme from an image, with options for light or dark mode and custom colors.

Instructions

Generate a complete Material Design 3 theme from an image

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": {
      "imageData": "<imageData>"
    },
    "name": "generate_theme_from_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
isDarkNoGenerate dark theme (false for light theme)
imageDataYesImage data with RGBA values (at most 65536 pixels; downscale larger images)
includeCustomColorsNoInclude custom colors from image

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already establish that the operation is read-only, non-destructive, idempotent, and closed-world. The description adds the Material Design 3 target and claims a 'complete' theme, but does not explain what that theme contains, how it is derived, or what form the result takes, which is a notable gap without an output schema.

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?

A single front-loaded sentence efficiently states the action, input, and output with no filler. Its limited coverage is assessed in the other dimensions rather than being a structural or verbosity problem.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The detailed schema and safety annotations make basic invocation possible, but the definition provides minimal support for confident selection and result interpretation. In particular, the absence of both an output schema and any elaboration of 'complete Material Design 3 theme' leaves the returned structure and format unclear.

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%, including the RGBA data layout, pixel limits, dark-mode option, and custom-color option, so the baseline score applies. The description only conveys that an image is the source and adds no parameter meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and identifies both the source and deliverable: generating a Material Design 3 theme from an image. It does not explicitly differentiate this image-based workflow from siblings such as generate_material_theme or extract_image_colors.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The intended scenario is clear enough to infer: use an image as the basis for a Material Design 3 theme. However, there is no explicit when-to-use or when-not-to-use guidance, nor any routing to a sibling for different inputs or desired outputs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.