Skip to main content
Glama

Brandize

by me.brandize

generate_logo

Generate a brand logo. Before calling, collect a short design brief from the user — do not assume defaults: (1) which package/tier they want to buy, (2) visual style, (3) color scheme (a primary brand color, and a secondary/accent if they want one), (4) layout (icon-only, wordmark, horizontal-lockup, or stacked), (5) the primary surface it must read well on, and (6) the industry. Ask for anything the user has not stated; if they have no preference on a field, propose an option and confirm it before generating. Returns a watermarked low-res preview plus a short checkout link priced at the Brandize service tiers, and an upgrades list of higher tiers (what each adds + its price) — offer these to the user before checkout and let them upgrade if they want, but never force it. The full-resolution, watermark-free deliverable (PNG + vector SVG + commercial license) unlocks only after payment — poll get_logo_result with the returned jobToken to retrieve it. This is a paid purchase: you must obtain the user's explicit acceptance of the Terms of Service and Privacy Policy and pass acceptedTerms=true before generating. Collect that consent the same way as the brief choices — give the user both policy links and ask it as a multiple-choice question ("Accept Terms & Privacy" / "Decline").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tierYesDelivery tier — ask the user which package they want to buy; do not assume one. PREMIUM: full-resolution PNG, vector SVG and a commercial license. COMPLETE: adds alternate logo variations (assembled after payment). BRAND_STARTER / BRAND_KIT: full brand-kit packages (lockups, favicons, palettes, collateral; BRAND_KIT adds social assets, app icons and brand documents). Use get_pricing_tiers to show the user prices if they want to compare before choosing.
styleYesVisual style. Ask the user which style they want.
industryYesIndustry category — ask the user; use "other" only if it genuinely fits none.
brandNameYesThe brand or product name.
whatItDoesYesOne short phrase describing what the brand does.
colorPrimaryYesDominant brand color as a 6-digit hex. Ask the user for their color scheme; if unsure, propose one and confirm.
layoutIntentYesLogo layout (icon-only, wordmark, horizontal-lockup, stacked). Ask the user.
acceptedTermsYesThe purchase is gated on Terms & Privacy consent. Before generating, give the user the Terms of Service and Privacy Policy links (returned by this tool on refusal, and on the /pay checkout page) and ask them to accept as a multiple-choice question — "Accept Terms & Privacy" / "Decline" — the same way you collected style, color scheme and layout. Pass true ONLY after the user picks accept; if they decline, stop and do not generate. The checkout page will also require them to accept.
antiReferenceNoAnything the logo should avoid looking like.
colorSecondaryNoOptional secondary/accent color as a 6-digit hex. Offer it as part of the color scheme.
primaryUseSurfaceYesPrimary surface the logo must read well on. Ask the user.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden, and it does so thoroughly. It discloses that this is a paid purchase, that output is a watermarked low-res preview, that full-resolution files unlock only after payment, that acceptedTerms=true is mandatory, and that an upgrades list should be offered but not forced. There is no contradiction with any annotation because none exist.

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?

The description is long, but the length is justified by the number of critical workflow requirements: brief collection, consent, pricing, upgrades, and post-payment retrieval. Key constraints are front-loaded ('Before calling', 'This is a paid purchase') so an agent encounters the most important operational rules first, and there is minimal 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?

Given 11 parameters, no annotations, and no output schema, the description is remarkably complete. It explains the return value (watermarked preview, checkout link, upgrades list), the post-payment retrieval mechanism (poll get_logo_result with jobToken), legal/consent preconditions, and how to handle user uncertainty. An agent has enough context to execute the tool correctly from start to finish.

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 description coverage is 100%, so the baseline is 3. The description adds real value beyond the schema by explaining the user-interaction workflow: collect the brief before calling, ask for anything not already stated, propose-and-confirm when the user has no preference, and handle acceptedTerms as a multiple-choice consent question. This turns static parameter names into a concrete collection procedure.

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 states a specific action ('Generate a brand logo') and then precisely defines the tool's scope: a paid logo purchase that returns a preview and checkout link, not the full deliverable. It also distinguishes from siblings by pointing to get_logo_result for full-resolution retrieval and get_pricing_tiers for price comparison, and by calling out that variations are part of upgrade tiers rather than this initial generation call.

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?

The description gives explicit, actionable when-to-call conditions: collect a design brief first, never assume defaults, ask about any missing field, propose and confirm options when the user has no preference, offer upgrades before checkout, and obtain explicit Terms/Privacy consent. It also provides a clear when-not case: if the user declines consent, stop and do not generate.

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

All Brandize toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool targets a distinct resource or action: logo generation, logo variations, variation purchase, result polling, color palette, meta tags, schema markup, pricing, blog search, and health check. The two logo-generation tools are clearly differentiated by new-job vs existing-job workflows, so an agent should not confuse them.

Naming Consistency4/5

Most tools follow a clean verb_noun convention: generate_logo, generate_color_palette, get_logo_result, search_blog, buy_logo_variation. The lone echo and the singular/plural mismatch between buy_logo_variation and generate_logo_variations are minor deviations from an otherwise consistent pattern.

Tool Count5/5

With 10 tools, the server is well scoped. The paid logo workflow is covered by generate, vary, buy, and retrieve tools, while supporting tools for palettes, SEO metadata, pricing, and blog search each serve a distinct purpose without bloat.

Completeness4/5

The core logo lifecycle is well covered: generate, create variations, purchase a variation, and retrieve the paid deliverable. However, the descriptions advertise upgrades and revision credits but provide no explicit tool to purchase or apply them, leaving a minor gap that agents must work around.

Resources