Skip to main content
Glama
Brand-System

@brandsystem/mcp

Official

brand_init

Initialize a brand configuration directory with empty scaffold. Use when you need to set up the directory structure without extracting brand data.

Instructions

Initialize a .brand/ directory with empty config scaffold. Low-level tool — prefer brand_start instead, which calls this automatically and also presents extraction options. Only use brand_init directly if you need to set up the directory without running extraction. Returns list of created files.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
industryNoIndustry vertical (e.g. 'content marketing agency')
client_nameYesCompany or brand name
website_urlNoPrimary website URL for web extraction
figma_file_keyNoFigma file key for design token extraction
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that the tool returns a list of created files, which adds transparency. However, it does not mention behavior on existing directories or potential side effects.

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 sentences, front-loaded with the main purpose, efficient and well-structured. No wasted words.

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

Completeness4/5

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

Given the tool's simplicity (4 params, no output schema), the description covers purpose, usage, and return value. Could mention extraction options briefly but not necessary since sibling covers it.

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 100%, meaning the schema already describes each parameter. The description does not add extra meaning or usage context beyond the schema, so baseline 3 is appropriate.

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 clearly states the tool initializes a .brand/ directory with an empty config scaffold, and explicitly contrasts with brand_start, which does extraction as well.

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?

Explicitly says it's a low-level tool, recommends using brand_start instead, and specifies the only direct-use case. Provides clear when-to-use and when-not-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Brand-System/brandsystem-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server