Skip to main content
Glama

iconify

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Icons

get_icons
Read-onlyIdempotent

Get SVG code and dimensions for specific icons. Input icon names in prefix:name format (e.g., "mdi:home", "fa:star"). Returns SVG markup, width, and height.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
iconsYesComma-separated icon names within the collection (e.g., "home,arrow-left,user")
prefixYesCollection prefix (e.g., "mdi", "fa", "heroicons", "lucide")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
iconsYesArray of icon objects with SVG data and dimensions
prefixYesCollection prefix (e.g., mdi, fa, heroicons)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "icons": {
+      "description": "Array of icon objects with SVG data and dimensions",
+      "items": {
+        "properties": {
+          "full_name": {
+            "description": "Full icon identifier in prefix:name format",
+            "type": "string"
+          },
+          "height": {
+            "description": "Icon height in pixels",
+            "type": "number"
+          },
+          "name": {
+            "description": "Icon name within the collection",
+            "type": "string"
+          },
+          "svg_body": {
+            "description": "SVG markup content (inner body)",
+            "type": "string"
+          },
+          "width": {
+            "description": "Icon width in pixels",
+            "type": "number"
+          }
+        },
+        "required": [
+          "name",
+          "full_name",
+          "svg_body",
+          "width",
+          "height"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "prefix": {
+      "description": "Collection prefix (e.g., mdi, fa, heroicons)",
+      "type": "string"
+    }
+  },
+  "required": [
+    "prefix",
+    "icons"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "icons": "home,arrow-left,user",
+    "prefix": "mdi"
+  },
+  {
+    "icons": "star",
+    "prefix": "fa"
+  }
+]
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish the tool as read-only, idempotent, and non-destructive. The description adds transparency by disclosing the return payload (SVG markup, width, height). It does not conflict with annotations and provides useful behavioral context beyond them.

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 extremely concise: two sentences that state the purpose, input format, and output. It is front-loaded with the main action and includes an example, earning its place without any fluff.

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?

For a simple retrieval tool with high schema coverage, an output schema, and comprehensive annotations, the description is complete. It covers input syntax, output contents, and the tool's purpose, leaving no significant gaps given the tool's simplicity.

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 coverage is 100% with descriptions for both parameters. The description adds extra semantics by explaining the prefix:name format and providing concrete examples, which goes beyond the schema's field descriptions. It reinforces the relationship between prefix and icons.

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's function: getting SVG code and dimensions for specific icons. It specifies the input format (prefix:name) and distinguishes itself from sibling tools like search_icons by focusing on retrieval of known icons rather than searching.

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 provides clear usage context: input icon names in prefix:name format, with examples. It does not explicitly mention exclusions or alternatives, but the specificity of 'for specific icons' implies when to use it. No alternative tools are referenced, so it misses the 'when not to use' guidance but is otherwise clear.

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

All iconify toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources