Skip to main content
Glama
borystam

mcp-visual-design-studio

by borystam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

brand_save

Destructive

Save a reusable brand kit locally, including palette, fonts, optional logo, and structured components, for consistent branding in future designs.

Instructions

Save a reusable local brand kit containing palette, bundled font names, optional logoAssetId and structured components.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv0.2.0
    • addedInput schema / $defs / __schema0 / properties / componentSource
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "componentId": {
+      "pattern": "^[A-Za-z0-9_-]{1,100}$",
+      "type": "string"
+    },
+    "systemId": {
+      "pattern": "^[A-Za-z0-9_-]{1,100}$",
+      "type": "string"
+    },
+    "systemVersion": {
+      "maxLength": 64,
+      "pattern": "^(?:0|[1-9][0-9]*)\\.(?:0|[1-9][0-9]*)\\.(?:0|[1-9][0-9]*)(?:-[A-Za-z0-9]+(?:[.-][A-Za-z0-9]+)*)?$",
+      "type": "string"
+    },
+    "variant": {
+      "pattern": "^[A-Za-z0-9_-]{1,100}$",
+      "type": "string"
+    }
+  },
+  "required": [
+    "systemId",
+    "systemVersion",
+    "componentId"
+  ],
+  "type": "object"
+}
    • removedInput schema / $defs / __schema0 / properties / style / properties / fontFamily / enum
      Removed value: -[
-  "Inter",
-  "Lora",
-  "monospace",
-  "sans-serif",
-  "serif"
-]
    • addedInput schema / $defs / __schema0 / properties / style / properties / fontFamily / pattern
      Added value: +"^[A-Za-z][A-Za-z0-9 _-]{0,79}$"
    • removedInput schema / $defs / __schema0 / properties / style / properties / fontWeight / anyOf
      Removed value: -[
-  {
-    "const": 400,
-    "type": "number"
-  },
-  {
-    "const": 500,
-    "type": "number"
-  },
-  {
-    "const": 600,
-    "type": "number"
-  },
-  {
-    "const": 700,
-    "type": "number"
-  }
-]
    • addedInput schema / $defs / __schema0 / properties / style / properties / fontWeight / maximum
      Added value: +900
    • addedInput schema / $defs / __schema0 / properties / style / properties / fontWeight / minimum
      Added value: +100
    • addedInput schema / $defs / __schema0 / properties / style / properties / fontWeight / type
      Added value: +"integer"
    • addedInput schema / $defs / __schema0 / properties / tokenBindings
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "background": {
+      "maxLength": 200,
+      "pattern": "^[A-Za-z][A-Za-z0-9_-]*(?:\\.[A-Za-z0-9_-]+)*$",
+      "type": "string"
+    },
+    "borderColor": {
+      "maxLength": 200,
+      "pattern": "^[A-Za-z][A-Za-z0-9_-]*(?:\\.[A-Za-z0-9_-]+)*$",
+      "type": "string"
+    },
+    "borderRadius": {
+      "maxLength": 200,
+      "pattern": "^[A-Za-z][A-Za-z0-9_-]*(?:\\.[A-Za-z0-9_-]+)*$",
+      "type": "string"
+    },
+    "borderWidth": {
+      "maxLength": 200,
+      "pattern": "^[A-Za-z][A-Za-z0-9_-]*(?:\\.[A-Za-z0-9_-]+)*$",
+      "type": "string"
+    },
+    "color": {
+      "maxLength": 200,
+      "pattern": "^[A-Za-z][A-Za-z0-9_-]*(?:\\.[A-Za-z0-9_-]+)*$",
+      "type": "string"
+    },
+    "fontFamily": {
+      "maxLength": 200,
+      "pattern": "^[A-Za-z][A-Za-z0-9_-]*(?:\\.[A-Za-z0-9_-]+)*$",
+      "type": "string"
+    },
+    "fontSize": {
+      "maxLength": 200,
+      "pattern": "^[A-Za-z][A-Za-z0-9_-]*(?:\\.[A-Za-z0-9_-]+)*$",
+      "type": "string"
+    },
+    "fontWeight": {
+      "maxLength": 200,
+      "pattern": "^[A-Za-z][A-Za-z0-9_-]*(?:\\.[A-Za-z0-9_-]+)*$",
+      "type": "string"
+    },
+    "gap": {
+      "maxLength": 200,
+      "pattern": "^[A-Za-z][A-Za-z0-9_-]*(?:\\.[A-Za-z0-9_-]+)*$",
+      "type": "string"
+    },
+    "letterSpacing": {
+      "maxLength": 200,
+      "pattern": "^[A-Za-z][A-Za-z0-9_-]*(?:\\.[A-Za-z0-9_-]+)*$",
+      "type": "string"
+    },
+    "lineHeight": {
+      "maxLength": 200,
+      "pattern": "^[A-Za-z][A-Za-z0-9_-]*(?:\\.[A-Za-z0-9_-]+)*$",
+      "type": "string"
+    },
+    "opacity": {
+      "maxLength": 200,
+      "pattern": "^[A-Za-z][A-Za-z0-9_-]*(?:\\.[A-Za-z0-9_-]+)*$",
+      "type": "string"
+    },
+    "padding": {
+      "maxLength": 200,
+      "pattern": "^[A-Za-z][A-Za-z0-9_-]*(?:\\.[A-Za-z0-9_-]+)*$",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • removedInput schema / properties / brand / properties / fonts / properties / body / enum
      Removed value: -[
-  "Inter",
-  "Lora",
-  "monospace",
-  "sans-serif",
-  "serif"
-]
    • addedInput schema / properties / brand / properties / fonts / properties / body / pattern
      Added value: +"^[A-Za-z][A-Za-z0-9 _-]{0,79}$"
    • removedInput schema / properties / brand / properties / fonts / properties / heading / enum
      Removed value: -[
-  "Inter",
-  "Lora",
-  "monospace",
-  "sans-serif",
-  "serif"
-]
    • addedInput schema / properties / brand / properties / fonts / properties / heading / pattern
      Added value: +"^[A-Za-z][A-Za-z0-9 _-]{0,79}$"
  2. First observedv0.1.1

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the description need not restate that this is a write operation. It adds the context 'local' and 'reusable', which hints at scope but does not explain what gets destroyed or overwritten (e.g., whether saving with an existing id replaces it). This is minimal additional transparency beyond the annotations.

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?

The description is a single, information-dense sentence. It front-loads the primary action and resource, then lists the key contained elements without redundancy. Every word contributes value, and nothing extraneous is included.

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?

Given the large nested schema, the destructive hint, and the absence of an output schema, the description is too sparse. It does not explain side effects (e.g., overwrite behavior), when to use the tool, or what 'local' means in relation to shared design systems. An agent calling this tool would still need to infer significant behavioral details.

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?

Schema description coverage is 0%, so the description must compensate. It does map high-level concepts to schema fields: 'palette' → colors, 'bundled font names' → fonts, 'optional logoAssetId' → logoAssetId, and 'structured components' → components. This helps the agent understand the payload's intent. However, it does not explain required fields like id and name, nor the structure of the components, so compensation is only partial.

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 clear verb ('Save') and resource ('reusable local brand kit'), and lists the key contents (palette, bundled font names, optional logoAssetId, structured components). However, it does not explicitly differentiate from sibling tools like brand_apply or design_system_save, so an agent must infer which tool is appropriate from context.

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?

No guidance is provided on when to use this tool versus alternatives. There are no conditions, prerequisites, or exclusions mentioned, leaving the agent to guess whether to use brand_save, design_system_save, or another sibling.

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

Deploy Server

Other Tools