Skip to main content
Glama

asset_init_brand

Initialize brand configuration by scaffolding brand.json and ensuring an assets directory exists. Auto-detects framework and returns platform hints. Call at project start to establish a brand source-of-truth for asset generation.

Instructions

Scaffold brand.json in the project root + ensure the assets dir exists. MCP equivalent of the brand.json portion of p2a init. Auto-detects the framework (Next.js, Expo, Flutter, Xcode, Astro, Vite, Remix, Nuxt, React Native, Electron, Node) and returns platform hints. Deliberately does NOT do IDE MCP registration — that's the one piece the user handles once at install time via a terminal. Call this at the start of a new project so subsequent generator calls have a brand source-of-truth and a known output dir.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_nameYesApp / brand name. Goes into brand.json and any PWA manifest.
paletteNoBrand palette as hex strings. Defaults to ['#2563eb', '#ffffff'].
assets_dirNoWhere generated assets should live. Defaults to the framework's conventional dir.
display_fontNoDisplay font family. Defaults to Inter.
body_fontNoBody font family. Defaults to Inter.
do_notNoBrand constraints to inject as negative anchors. Defaults to drop-shadows / heavy-gradients / skeuomorphic-bevels.
overwriteNoWhen true, overwrites an existing brand.json.
cwdNoProject root. Defaults to process.cwd().
Behavior5/5

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

Discloses auto-detection of framework, return of platform hints, and that it does not handle IDE registration. No contradiction with 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?

Two concise sentences (three in original) front-load the action and add key usage context without redundancy.

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?

With 8 parameters and no output schema, the description covers when and why to use it. Missing detail on return format, but sufficient for an agent.

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 coverage is 100%, so description adds minimal value beyond naming parameters. However, it contextualizes the overall tool purpose.

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?

Clearly states the verb 'scaffold' and the resources 'brand.json' and 'assets dir.' Differentiates itself from sibling tools like asset_generate_app_icon by specifying it's the initial setup step.

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 'call this at the start of a new project' and explains what it deliberately does not do (IDE MCP registration), guiding the agent to use other tools after.

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/MohamedAbdallah-14/prompt-to-asset'

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