Skip to main content
Glama
Design Atlas MCP

Design Atlas MCP

by Tradelord223

create_brand_kit

Read-onlyIdempotent

Build a brand-specific responsive kit from a brief, returning source manifest, design tokens and contrast checks. Choose file output to receive one manifest's content, or full for the entire kit.

Instructions

Build a brand-specific responsive kit. Default returns the source manifest, tokens and contrast checks. Repeat the same brief with output=file and one manifest path to receive its content. Full returns the whole kit.

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": {
      "name": "<name>",
      "description": "<description>"
    },
    "name": "create_brand_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
pathNo
limitNo
voiceNo
accentNoSix-digit brand color, e.g. #285b42.
colorsNo
offsetNo
outputNo
packIdNo
radiusNo
audienceNo
headlineNo
platformNo
typographyNo
actionLabelNo
descriptionYes
contactEmailNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, closed-world operation, so the bar is lower. The description adds useful behavioral detail about the default response payload and the different output modes. It does not discuss rate limits or permissions, but those are less critical for this annotated read-only generator.

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?

The description is three sentences and front-loads the core purpose before explaining output modes. It is efficient and avoids filler. A small amount of clarity is lost in the phrase 'one manifest path', but overall it is well structured.

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

Completeness2/5

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

This is a complex tool with 17 parameters, nested objects, and no output schema, yet the description explains only the output modes. It does not describe how the required name and description form a brief, how the brand parameters interact, or what the summary mode returns. Given the low schema coverage, the description is not complete enough for reliable invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 6% across 17 parameters, so the description must compensate heavily. It only clarifies the output behavior and vaguely references a manifest path, while leaving name, description, colors, typography, packId, and most other parameters unexplained. It also never mentions the 'summary' enum value even though the schema includes it.

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 states a specific verb and resource: build a brand-specific responsive kit. It also clarifies that the tool returns generated artifacts rather than persisting them. However, it does not explicitly distinguish this tool from siblings such as import_brand_identity, audit_design, or get_design_pack.

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 description explains how to use the output modes: default returns manifest/tokens/contrast checks, output=file returns a manifest's content, and full returns the whole kit. It does not say when to choose this tool over sibling tools or what prerequisites are required. The usage guidance is therefore implied rather than explicit.

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