Skip to main content
Glama

logo_workflow

Run a logo design pipeline: audit SVGs, search a 1,400+ mark library, render previews, export favicon and app-icon variants, and build concept or presentation boards.

Instructions

Logo-design workflow. Select action: audit, search, renderers, render, export_variants, concept_sheet, preview_sheet, or presentation_board. Search queries the 1,400+ mark library; render/export/board actions write files.

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": {
      "action": "<action>"
    },
    "name": "logo_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
bgNoBackground colour for audit/render
icoNoFavicon .ico output path
outNoOutput PNG/HTML path
pngNoPNG sizes for export variants
caseNoSearch letter case
monoNoExtra one-colour hex variants
moodNoSearch mood adjective
nameNoBrand/output base name
onlyNoVariant subset: black, white, mono, square, favicon, app-icon
refsNoReference SVGs for shelf test
sizeNoSquare PNG size
specNoPresentation spec JSON path
typeNoSearch mark type
colorNoSearch colour family
filesNoSVG file paths for audit, render, concept, or preview
limitNoMax search results (default 25)
namesNoConcept labels
notesNoOne-line concept ideas
queryNoFree-text library query
titleNoAccessible output title
widthNoPNG width
actionYesLogo workflow step
aspectNoSearch aspect ratio
formatNoSearch output shape
heightNoPNG height
iconBgNoApp-icon tile colour
iconFgNoMark colour on app-icon tile
masterNoMaster SVG for export_variants
outDirNoOutput directory
pngDirNoPresentation slide PNG directory
backendNoRenderer backend
lockupsNoLockup SVG per concept
paddingNoPadding fraction (0-0.4)
subjectNoSearch visual subject
summaryNoAggregate library view
variantNomain|icon
geometryNoSearch geometry
icoSizesNoICO sizes, e.g. [16,32,48]
industryNoSearch industry
subtitleNoSheet subtitle
webIconsNoEmit favicon/web icon set
exemplaryNoOnly teaching examples
greyscaleNoRender concepts in greyscale
iconScaleNoMark size on app-icon tile
keepWhiteNoKeep pure white in mono variants
maxColorsNoMaximum distinct colours
minColorsNoMinimum distinct colours
recommendNo1-based recommended concept
refsCountNoShelf reference count
techniqueNoSearch technique
typeStyleNoSearch type style
brandColorNoPreview brand colour
listValuesNoPrint filter values
noGradientNoExclude gradients
symbolTypeNoSearch symbol type
compareOnlyNoPreview side-by-side only
listMockupsNoList presentation mockups
primaryColorNoDominant colour family
refsIndustryNoShelf reference industry
faviconSourceNoSimplified favicon SVG
opticalOffsetNoVertical square-output nudge

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations at all, the description carries the entire burden. It does earn credit for disclosing that render/export/board actions write files, which is the single most important safety fact here, but it says nothing about what gets overwritten, whether output directories are created, or what any action returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the action list, and no filler. The enumeration is long but is the necessary routing information; the only inefficiency is that the action names are listed without any per-action hint.

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?

For a tool with 61 parameters, eight actions, no annotations, and no output schema, a two-sentence description is far too thin; nothing explains per-action required parameters beyond the shared `action` field or what each action produces. Only the read-versus-write distinction is covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so each parameter is individually documented, but with 61 parameters split across eight disjoint action sets the critical missing meaning is which parameters apply to which action; the description provides no such mapping and does not group or exemplify any parameter. Because the schema cannot convey that cross-parameter structure, the description needed to and did not.

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 names the domain ("Logo-design workflow") and enumerates all eight actions verbatim, so an agent knows this is a multi-action dispatcher rather than a single-purpose tool. It stops short of explaining what each action does beyond grouping them into read (search) versus write (render/export/board).

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

Usage Guidelines3/5

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

"Search queries the 1,400+ mark library; render/export/board actions write files" gives an implicit read-vs-write routing cue, but no explicit when-to-use conditions and no comparison against plausible siblings such as design_audit, palette, or export_project. An agent must infer which of the eight actions fits its task.

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