Skip to main content
Glama

Brilliant Design (hosted)

Design on a Brilliant canvas

design

Use this when the user asks to design, mock up, wireframe or lay out a user interface or a page as an editable design: a website, landing or pricing page, an app screen (login, settings, checkout), a dashboard, a slide, a social post, a poster, an invitation, a menu or a business card, or a design to edit or tweak by hand. It opens a new, empty, live Brilliant canvas in the chat; the design is built there as editable layers (frames, text, shapes, icons). Not for generating a photograph or an illustration, for photo edits (use remove_background) or for questions that need no design. Do not use to change a design already open in this conversation. Rows take literal values (hex colors, numbers); design tokens are not available in this lane.

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": "design"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoA short name for the design.
intentNoOne plain line on what this design is about to hold, such as "A pricing section with three plans and a highlighted middle tier". The canvas shows it beside ChatGPT's cursor while the first rows are written.

Output Schema

NameRequiredDescriptionDefault
rowsNo
slugYes
turnYes
titleNo
statusYes
appliedNo
openUrlYes
playgroundUrlYes
placeholderCopyNo

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 declare a non-read-only, non-destructive, non-idempotent tool, and the description adds real context beyond that: it opens a NEW empty live canvas in the chat, the output is editable layers (frames, text, shapes, icons), and rows require literal values because design tokens are unavailable in this lane. It stops short of saying what happens to a canvas if the call is repeated or fails, 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?

Front-loaded with the trigger clause and the negative exclusions come after, so the important content is early. The long comma-separated artifact list is useful for matching but heavy; a bulleted or shorter enumeration would read more cleanly.

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?

An output schema exists, so return values need not be explained. For a state-creating design tool, the description covers trigger, exclusion, output form (editable layers), and input constraints — nothing an agent needs 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%, so title and intent are already fully documented; the description adds a value-format constraint ('rows take literal values (hex colors, numbers); design tokens are not available'), which is meaning the schema does not carry. It does not otherwise elaborate on the two parameters, so it is above baseline but not rich.

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?

Names a specific verb (design/mock up/wireframe) and resource (editable UI design), then enumerates concrete artifacts (landing page, app screen, dashboard, slide, business card). This is clearly distinguishable from remove_background (photos) and edit_design (changing an already-open design).

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 explicit when-to-use triggers ('when the user asks to design, mock up, wireframe...'), explicit when-not ('Not for generating a photograph or an illustration, for photo edits'), names an alternative tool (remove_background), and rules out changing an already-open design. Very little is left to inference.

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