Skip to main content
Glama

Set Brand Tool

set_brand
Idempotent

Create or replace a brand kit. Send every field you want to keep: omitted colors, fonts, logos and notes are cleared, so call get_brand first when editing. Colors are hex (#0f172a) or oklch(); fonts are Google Fonts family names or https URLs to .woff2 files. To use a logo you just rendered, pass its render_id as logo_render_id instead of a URL; every later render with this brand can then use it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>",
      "name": "<name>"
    },
    "name": "set_brand"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesDisplay name.
slugYesLowercase id with dashes, for example tailwind-weekly.
fontsNo
notesNoVoice, layout or usage notes for future renders.
colorsNoBecome Tailwind tokens: bg-brand-primary, text-brand-foreground and so on.
logo_urlNohttps URL of the logo for light backgrounds.
logo_dark_urlNohttps URL of the logo for dark backgrounds.
logo_render_idNorender_id of an earlier render to use as the logo, instead of logo_url. Its largest png is used (else webp, else jpeg).
logo_dark_render_idNorender_id to use as the dark-background logo, instead of logo_dark_url.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0
Behavior5/5

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

The description discloses a critical destructive behavior not covered by annotations: omitted colors, fonts, logos, and notes are cleared. It also explains format expectations, the logo_render_id alternative, and the downstream reuse of that logo in later renders. The idempotentHint annotation is consistent with create-or-replace semantics, not contradicted.

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 front-loaded with the create/replace intent, immediately followed by the destructive omission behavior and editing prerequisite. Four sentences carry the essential warnings and formats with no obvious filler.

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 nine-parameter nested mutation tool with no output schema, the description covers the critical behavior: replacement clears omitted fields, required editing workflow via get_brand, accepted color and font formats, and logo render references. Nothing essential to calling it correctly 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?

Schema coverage is high at 89%, so the schema already documents most parameters. The description adds useful operational meaning beyond the schema: send every field you want to keep, and a logo_render_id becomes reusable for every later render with the brand. Some format details repeat the schema, but the clearing and reuse semantics add real value.

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 first sentence states a specific verb and resource: "Create or replace a brand kit." This clearly distinguishes it from get_brand, list_brands, delete_brand, and render without needing to inspect the schema.

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?

It gives a concrete prerequisite for editing: "call get_brand first when editing," which directly supports safe use. It lacks an explicit when-not-to-use condition or comparison to other siblings, but the replace behavior itself makes the usage context clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources