Skip to main content
Glama
Sign In
media-gen-mcp

media-gen-mcp

by wangdong233
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

generate_icon

Fetch an icon from Iconify's 200k+ collection and render locally as SVG or PNG. Customize size, color, and format.

Instructions

Fetch and render a vector icon / logo / symbol / favicon (图标/logo/符号) from Iconify — 200k+ icons. Renders to SVG/PNG locally. Needs network (Iconify API); cached after first fetch. Browse at https://icon-sets.iconify.design. No AI. Multilingual triggers: アイコン · icono · icône · Symbol · значок · ícone (ja/es/fr/de/ru/pt).

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": {
      "icon": "<icon>"
    },
    "name": "generate_icon"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconYesIconify icon ID, format: SET:NAME. Common sets: mdi (Material Design), lucide (Lucide), logos (brand logos), fa-solid / fa-brands (Font Awesome). Examples: mdi:home, lucide:gem, logos:github, fa-brands:twitter. Browse all at https://icon-sets.iconify.design
nameNoOutput filename (without extension); defaults to sanitized icon ID
sizeNoPixel size (square), default 128
colorNoForeground color (default currentColor; PNG defaults to black)
formatNosvg
outDirNoOutput directory, default session-dir/output

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.7
    • addedInput schema / properties / icon
      Added value: +{
+  "description": "Iconify icon ID, format: SET:NAME. Common sets: mdi (Material Design), lucide (Lucide), logos (brand logos), fa-solid / fa-brands (Font Awesome). Examples: mdi:home, lucide:gem, logos:github, fa-brands:twitter. Browse all at https://icon-sets.iconify.design",
+  "type": "string"
+}
    • changedInput schema / properties / name / description
      Previous value: -"Icon name as prefix:name, e.g. mdi:home, logos:github, lucide:check. Also used (sanitized) as the output filename."New value: +"Output filename (without extension); defaults to sanitized icon ID"
    • changedInput schema / required
      Previous value: -[
-  "name"
-]New value: +[
+  "icon"
+]
  2. First observedv0.3.7

TDQS

A4.2/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses network requirement, caching, local rendering, SVG/PNG support, and no AI involvement. However, it omits details on error handling or limitations like maximum size.

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

Conciseness5/5

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

The description is two sentences plus a multilingual line, very concise and front-loaded with the main purpose. Every sentence adds value, no redundancy.

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

Completeness4/5

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

Given 6 parameters and no output schema, the description covers purpose, network, caching, format, and browsing reference. It lacks error handling details but is otherwise complete for a fetch-and-render tool.

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 coverage is high (83%), so baseline is 3. The description adds examples of icon IDs and mentions multilingual triggers, but does not significantly enhance parameter understanding beyond the schema. The schema already describes each parameter sufficiently.

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 clearly states the tool fetches and renders vector icons from Iconify, with specific verb 'Fetch and render' and resource 'vector icon / logo / symbol / favicon'. It distinguishes from sibling tools like generate_image and generate_chart by specifying the icon library scope.

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

Usage Guidelines4/5

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

The description mentions network dependency and caching, but does not explicitly compare with sibling tools or state when not to use. It implies usage for icon generation but lacks explicit alternatives or exclusions.

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

Deploy Server

Other Tools