Skip to main content
Glama

generate_icon

Create app icons, avatars, and stickers as small, recognizable visual assets optimized for clarity at small sizes.

Instructions

Generate icons, avatars, and stickers - small visual assets optimized for clarity at small sizes.

Use this when:

  • Creating app or website icons

  • Generating user avatars or profile pictures

  • Creating stickers for messaging apps

  • Need small, recognizable visual assets

NOT for:

  • Logos with text or business branding (use generate_logo instead)

  • Large detailed images (use generate_image instead)

  • Editing existing icons (use edit_image instead)

Chain with: If user requests specific pixel dimensions for icons (e.g., 512x512, 192x192), chain with resize_image after generation.

Example: "generate_icon description='shopping cart' purpose='icon' style='outlined'"

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": {
      "description": "<description>",
      "purpose": "<purpose>",
      "style": "<style>",
      "size": "<size>",
      "transparentBackground": "<transparentBackground>"
    },
    "name": "generate_icon"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeYes256
styleYesflat
purposeYesicon
fileNameNo
descriptionYes
backgroundColorNo
transparentBackgroundYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.2

TDQS

A3.9/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 does disclose the design intent (optimization for legibility at small sizes) and the chaining pattern with resize_image, which is genuinely useful. However, it says nothing about generation latency, whether the call is synchronous, cost/credit implications, what the response contains, or how transparentBackground interacts with backgroundColor.

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 summary followed by clearly labeled use/avoid/chain sections and a worked example — easy to scan and every section earns its place. Minor waste in restating 'small, recognizable visual assets' after the opening line already said it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter, 5-required generation tool with no annotations and no output schema, the usage/routing story is complete but the invocation story is thin. An agent knows which tool to pick yet still lacks guidance on backgroundColor vs transparentBackground precedence and whether fileName affects the returned asset identifier.

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 7 parameters, and 5 are required, so the description must compensate and largely does not. Only description, purpose, and style appear in the example; size, transparentBackground, backgroundColor, and fileName get no prose explanation, and the author's own example contradicts the schema by omitting the three required non-exampled fields. The enums are self-explanatory, which limits the damage but does not fill the gap.

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 opens with a specific verb and resource set (icons, avatars, stickers) and immediately qualifies the output as 'small visual assets optimized for clarity at small sizes'. It actively distinguishes itself from generate_logo, generate_image, and edit_image, so an agent can route without inspecting any schema.

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 explicit positive triggers (app/website icons, avatars, messaging stickers), explicit exclusions with named alternatives for each ('NOT for: logos with text... use generate_logo instead'), and even a chaining rule to resize_image for exact pixel dimensions. This is close to the ideal of when/when-not/alternatives.

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