Skip to main content
Glama

generate_logo

Create business or brand logos with text, taglines, custom colors, and style options for branding projects.

Instructions

Generate professional logos with text support and multiple style options for branding.

Use this when:

  • Creating a logo for a business or brand

  • Need text-integrated logo design

  • Want specific brand colors in the logo

  • Need icon-only logo (no text)

NOT for:

  • Simple icons without branding context (use generate_image instead)

  • General images not for branding (use generate_image instead)

  • Editing existing logos (use edit_image instead)

Chain with: If user requests specific pixel dimensions for the logo, chain with resize_image after generation.

Example: "generate_logo businessName='TechStart' tagline='Innovation Made Simple' style='modern'"

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": {
      "businessName": "<businessName>",
      "style": "<style>",
      "iconOnly": "<iconOnly>",
      "aspectRatio": "<aspectRatio>",
      "transparentBackground": "<transparentBackground>",
      "outputVariants": "<outputVariants>"
    },
    "name": "generate_logo"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleYesmodern
taglineNo
fileNameNo
iconOnlyYes
aspectRatioYes1:1
businessNameYes
primaryColorNo
outputVariantsYes
secondaryColorNo
businessDescriptionNo
transparentBackgroundYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.2

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It adds real value by disclosing the post-generation chaining pattern with resize_image, but it never states what the tool returns (image URL, file, variants), whether generation is synchronous or long-running, or whether there is any cost or permission implication for an 11-parameter generation call.

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?

Front-loaded purpose sentence followed by scannable when/NOT-for/chain sections, which is the right shape for a routing-heavy tool. Minor waste: the 'use generate_image instead' parenthetical is repeated twice, and the example line duplicates information already given.

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 mutation-style generation tool with no annotations, no output schema, and 11 undocumented parameters, the definition covers routing well but omits the two things an agent most needs after selection: what the call returns and what the required-but-unexplained parameters (aspectRatio, outputVariants, transparentBackground) do.

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 description coverage is 0% across 11 parameters (6 required), so the description must compensate and largely does not. It clarifies businessName, tagline, style, and colors by implication through the example, but leaves aspectRatio, transparentBackground, outputVariants, businessDescription, and fileName completely unexplained in both schema and description.

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?

States a specific verb and resource ('Generate professional logos') plus distinguishing scope: text support, style options, branding context. The NOT-for section explicitly separates it from generate_image and edit_image, so an agent can pick the right sibling without opening schemas.

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?

Provides an explicit when-to-use list (business/brand logo, text-integrated, brand colors, icon-only), a NOT-for list naming concrete alternatives (generate_image, edit_image), and even a chaining rule with resize_image. There is no ambiguity about selection.

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