Skip to main content
Glama

Analyze Design

analyze_design

Analyzes a design image from a file path or URL and returns a structured JSON spec covering layout, colors, typography, spacing, components, and style keywords.

Instructions

Analyze a design image (local file path or URL) and return a structured JSON spec: layout, colors, typography, spacing, components and style keywords.

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": "<image>"
    },
    "name": "analyze_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYesLocal file path or http(s) URL of the design image

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses that the output is a structured JSON spec and names the categories, which is useful minimum-viable context. It does not cover supported image formats, file access requirements, error behavior, or processing limitations.

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?

The definition is a single front-loaded sentence with no redundant wording. The purpose and return categories are stated compactly and nothing obvious could be removed without losing information.

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?

For a simple one-parameter tool, the description covers the essential purpose and broadly lists return categories. Because there is no output schema, it stops short of describing the exact JSON structure, image format support, or failure modes, leaving some gaps for an agent relying solely on this definition.

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?

The single image parameter is fully described in the schema as a local file path or http(s) URL. The description repeats the same input forms and adds no further syntax, format constraints, or example values. With 100% schema coverage, a baseline 3 is appropriate.

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 gives a specific verb and resource: analyze a design image and return a structured JSON spec. It lists the spec categories, which distinguishes it from purely generative or critique-oriented siblings in spirit. However, it does not explicitly differentiate itself from tools like critique_design or design_to_prompt.

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

Usage Guidelines2/5

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

The description states what the tool does and acceptable input forms, but gives no when-to-use guidance, no exclusions, and no comparison to alternatives. An agent must infer from the purpose alone whether this is the right tool versus critique_design or extract_tokens.

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