Skip to main content
Glama

generate_infographic

Create AI-powered infographic images from content descriptions, with customizable styles, layouts, colors, and fonts for presentations, social media, and visual summaries.

Instructions

Generate AI-powered infographic images from content descriptions with customizable styles, layouts, and branding.

Use this when:

  • Creating visual summaries of data, processes, or concepts

  • Generating infographics for presentations or social media

  • Visualizing comparisons, timelines, or step-by-step guides

  • Creating branded infographics with specific colors and fonts

NOT for:

  • Simple image generation without data/content (use generate_image instead)

  • Editing existing infographics (use edit_image instead)

  • Logo or icon creation (use generate_logo instead)

  • Product photography (use generate_product instead)

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

Example: "generate_infographic content='5 steps to improve productivity: 1. Set goals 2. Prioritize tasks 3. Eliminate distractions 4. Take breaks 5. Review progress' style='corporate' layout='vertical'"

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": {
      "content": "<content>",
      "style": "<style>",
      "layout": "<layout>",
      "outputFormat": "<outputFormat>",
      "quality": "<quality>"
    },
    "name": "generate_infographic"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleYesminimal
layoutYesvertical
contentYes
qualityYes
brandFontNo
iconHintsNo
aspectRatioNo
brandColorsNo
outputFormatYespng
outputFilenameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.2

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses that generation is AI-driven and that a downstream resize step may be needed, but says nothing about latency, cost, permissions, or whether repeated calls with identical inputs produce identical output — all material for an image-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 with a one-sentence purpose, then clearly headed sections for when-to-use, exclusions, and chaining, closing with a concrete example. It runs long, and the four-bullet "Use this when" list partly restates the opening sentence, but no section is wasted.

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?

Selection guidance is excellent for a 10-parameter tool with no annotations and no output schema. However, with 5 required parameters and zero schema descriptions, the definition leaves an agent unable to reason about half the inputs, and it does not describe the shape of the returned image reference.

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

Parameters3/5

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

Schema description coverage is 0% across 10 parameters, so the description must compensate and only partly does. It adds meaning for content and style via the worked example and implies branding through brandColors/brandFont, but aspectRatio, outputFormat, quality, outputFilename, and iconHints are never mentioned, nor are the hex-format and max-items constraints.

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 AI-powered infographic images") plus the scope of customization (styles, layouts, branding). It explicitly distinguishes itself from generate_image, edit_image, generate_logo, and generate_product, so an agent can route correctly without inspecting sibling 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 "Use this when" list, a "NOT for" list that names the correct alternative for each excluded case, and a chaining rule (resize_image when pixel dimensions are requested). 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.