Skip to main content
Glama
Design Atlas MCP

Design Atlas MCP

by Tradelord223

import_brand_identity

Read-onlyIdempotent

Extract brand colors, fonts, radii, name and description from HTML or CSS, then return evidence, unknowns and a brief for building a brand kit locally.

Instructions

Extract declared brand colors, font families, radius, name and description from supplied HTML or CSS. Returns the evidence, unknowns and a brief for create_brand_kit. Runs locally.

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

Input Schema

NameRequiredDescriptionDefault
cssNo
htmlNo
nameNo
overridesNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new context: 'Runs locally' (no external calls) and that the result includes 'evidence' and 'unknowns', implying partial or low-confidence extraction is surfaced rather than hidden.

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?

Two sentences, no filler, with the extraction scope front-loaded before the handoff target. 'Runs locally' is a short, high-value trailing note rather than padding.

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?

With no output schema, the mention of evidence/unknowns/brief is a useful partial return-value sketch, and the pipeline relationship is clear. However, for a tool with a nested overrides parameter, zero schema descriptions and all-optional inputs, the definition leaves too much about invocation unexplained.

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 0% across 5 parameters including a nested overrides object, so the description must carry the load. It only hints at the extracted fields and never explains the html vs css inputs (both optional), what overrides does, or the size limits — an agent cannot tell how to use overrides from this text.

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?

The description opens with a specific verb ('Extract') and an enumerated resource ('declared brand colors, font families, radius, name and description'), plus the input sources (HTML or CSS). 'Declared' narrows the scope meaningfully, distinguishing this from any tool that audits or infers styles, and it names create_brand_kit as the downstream consumer.

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?

Usage is only implied through 'a brief for create_brand_kit', which situates the tool at the front of a pipeline. There is no explicit statement of when to prefer this over audit_design or get_design_pack, and no guidance on what to do when extraction yields nothing usable.

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