brandsystem-mcp

Generate brand report

brand_report

Idempotent

Generate a self-contained HTML brand identity report with embedded logos, colors, typography, and tokens; upload it to any AI chat as offline brand guidelines.

Instructions

Generate a portable HTML brand identity report with embedded logos, color swatches, typography, and tokens. The HTML is self-contained and works offline — upload it to any AI chat (Claude, ChatGPT, Gemini) as instant brand guidelines. Written to .brand/brand-report.html. Use after brand_compile. Returns file path, report summary (color/font/logo counts), and a ready-to-copy Brand Instructions text block.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`_metadata`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.17.0Oct 25, 2026
Removedv0.14.1Jul 18, 2026

Changed1 schema field changedv0.11.0Jul 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "_metadata": {
+      "additionalProperties": true,
+      "properties": {
+        "next_steps": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "what_happened": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "what_happened",
+        "next_steps"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "_metadata"
+  ],
+  "type": "object"
+}

First observedv0.5.0Apr 14, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and idempotentHint=true; the description adds useful behavior beyond that — output is a written file at a specific path, the HTML is self-contained and works offline. It doesn't discuss whether re-running overwrites the prior report, though idempotentHint implies it. No contradiction with the write annotation.

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?

Three front-loaded sentences: what it produces, how it behaves (offline/self-contained) and where it writes, then the sequencing prerequisite and return contents. No filler or repetition of the title.

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?

For a zero-parameter tool with an output schema and full annotations, this covers everything an agent needs: prerequisite order, write location, artifact portability, and what comes back. Nothing critical 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?

Zero parameters, so the baseline is 4. The description correctly presents this as a no-argument operation and focuses on output artifacts instead of inventing configuration options.

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?

States a specific verb and artifact: 'Generate a portable HTML brand identity report' with the exact contents (logos, color swatches, typography, tokens). The output location '.brand/brand-report.html' makes it unmistakable versus siblings like brand_export or brand_compile.

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

Usage Guidelines4/5

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

Gives an explicit prerequisite ('Use after brand_compile') and a concrete downstream use case (upload to an AI chat as brand guidelines). It does not name when to skip it or contrast with brand_export, which is the main remaining gap.

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

Deploy Server