Skip to main content
Glama

Critique Design

critique_design

Analyze a design image to score hierarchy, spacing, color, typography, consistency, and usability, then return strengths, prioritized issues with fixes, and quick wins.

Instructions

Get a rigorous senior-designer critique of a design: scores for hierarchy, spacing, color, typography, consistency and usability, plus strengths, prioritized issues with fixes, and quick wins.

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": "critique_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

A3.5/5.0
Behavior4/5

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

No annotations exist, so the description carries the full behavioral burden, and it does more than most: it discloses the shape of the return value (per-dimension scores plus strengths, prioritized issues with fixes, and quick wins). What it omits is whether the operation is purely read-only (implied but unstated), any size/format constraints on the input image, and cost or latency characteristics.

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?

One sentence, front-loaded with the verb and resource before the deliverable list. The six-dimension enumeration is long but each item is substance, not filler; nothing could be cut without losing information an agent would want.

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

Completeness4/5

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

For a one-parameter image-analysis tool with no output schema, the description is close to sufficient: purpose and return contents are both explicit. The remaining gap is sibling disambiguation against analyze_design, which is the one thing an agent most needs before invoking this over its near-neighbor.

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?

There is a single required parameter with 100% schema description coverage, so the schema already fully explains that image accepts a local path or http(s) URL. The description adds no meaning beyond that, which matches the baseline-3 rule when the schema does the work.

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?

"Get a rigorous senior-designer critique of a design" names a specific verb and resource, and the colon list enumerates exactly what the critique contains (six scored dimensions, strengths, prioritized issues with fixes, quick wins). It falls short of 5 because it never distinguishes itself from the closely-named sibling analyze_design, so an agent cannot route between them from the text alone.

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 says nothing about when to choose this over analyze_design, compare_designs, or audit_accessibility, all of which plausibly accept a design image. There are no stated prerequisites, no exclusions, and no indication of whether it works on a single screen or a multi-screen flow.

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