Supericons

Get Icon

get_icon

Retrieve one exact SVG icon using an exact ref returned by search_icons, recommend_icons, or preview_icons. Do not guess icon IDs. Use search_icons first if the user only described a concept. Returns SVG code, explicit public library labels, visual preview URL, and public semantic guidance for the exact icon.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Exact icon ID without the library prefix, for example "database", "user-circle", "brain-circuit", or "arrow-down".
`style`	No	Optional style preference. Material Symbols supports outline and solid. Other hosted libraries report their verified styles in list_libraries.	any
`library`	Yes	Required library key for the exact icon. Supported values include si (Supericons AI and developer tool logos), lucide, tabler, phosphor, heroicons, bootstrap, iconoir, ionicons, material, simpleicons (Simple Icons brand logos), and mingcute.

Output Schema

TableJSON Schema

Name	Required	Description
`code`	No	Stable error code when the exact icon is unavailable.
`hint`	No	Plain-language explanation of how to recover.
`icon`	No	Exact matching icon when found.
`error`	No	Recoverable error message when no exact icon is found.
`next_step`	No	Recommended next tool action.
`retryable`	No	Whether repeating the same exact lookup may succeed.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedJul 31, 2026

addedOutput schema / properties / code

Added value: +{
+  "description": "Stable error code when the exact icon is unavailable.",
+  "type": "string"
+}

addedOutput schema / properties / hint

Added value: +{
+  "description": "Plain-language explanation of how to recover.",
+  "type": "string"
+}

addedOutput schema / properties / next_step

Added value: +{
+  "description": "Recommended next tool action.",
+  "type": "string"
+}

addedOutput schema / properties / retryable

Added value: +{
+  "description": "Whether repeating the same exact lookup may succeed.",
+  "type": "boolean"
+}

Changed1 schema field changedJul 15, 2026

changedInput schema / properties / style / description

Previous value: -"Optional style preference. Use \"any\" unless the caller needs a specific variant."New value: +"Optional style preference. Material Symbols supports outline and solid. Other hosted libraries report their verified styles in list_libraries."

Changed1 schema field changedJul 15, 2026

changedInput schema / properties / style / description

Previous value: -"Optional style preference. Material Symbols supports outline and solid. Other hosted libraries report their verified styles in list_libraries."New value: +"Optional style preference. Use \"any\" unless the caller needs a specific variant."

Changed1 schema field changedJul 15, 2026

changedInput schema / properties / style / description

Previous value: -"Optional style preference. Use \"any\" unless the caller needs a specific variant."New value: +"Optional style preference. Material Symbols supports outline and solid. Other hosted libraries report their verified styles in list_libraries."

Changed9 schema fields changedJul 3, 2026

changedInput schema / properties / library / description

Previous value: -"Required library key for the exact icon. Supported values include si, lucide, tabler, phosphor, heroicons, bootstrap, iconoir, ionicons, material, simpleicons, and mingcute."New value: +"Required library key for the exact icon. Supported values include si (Supericons AI and developer tool logos), lucide, tabler, phosphor, heroicons, bootstrap, iconoir, ionicons, material, simpleicons (Simple Icons brand logos), and mingcute."

addedOutput schema / properties / icon / properties / icon_preview_url

Added value: +{
+  "description": "Browser URL for visual inspection of this icon.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / icon / properties / icon_ref

Added value: +{
+  "description": "Stable icon reference in library:id format.",
+  "type": "string"
+}

addedOutput schema / properties / icon / properties / libraryName

Added value: +{
+  "description": "Legacy camelCase public source library name.",
+  "type": "string"
+}

addedOutput schema / properties / icon / properties / library_key

Added value: +{
+  "description": "Source icon library key repeated for explicit agent display.",
+  "type": "string"
+}

addedOutput schema / properties / icon / properties / library_label

Added value: +{
+  "description": "Public source library label, for example Supericons (si).",
+  "type": "string"
+}

addedOutput schema / properties / icon / properties / library_name

Added value: +{
+  "description": "Public source library name, for example Supericons or Simple Icons.",
+  "type": "string"
+}

addedOutput schema / properties / icon / properties / search_preview_url

Added value: +{
+  "description": "Browser URL for visual inspection of the source search results.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / properties / icon / required

Previous value: -[
-  "id",
-  "name",
-  "library",
-  "type",
-  "style",
-  "svg"
-]New value: +[
+  "id",
+  "name",
+  "library",
+  "library_key",
+  "library_name",
+  "library_label",
+  "icon_ref",
+  "icon_preview_url",
+  "type",
+  "style",
+  "svg"
+]

Changed1 schema field changedJun 27, 2026

changedInput schema / properties / library / description

Previous value: -"Required library key for the exact icon. Supported values include lucide, tabler, phosphor, heroicons, bootstrap, iconoir, ionicons, material, simpleicons, and mingcute."New value: +"Required library key for the exact icon. Supported values include si, lucide, tabler, phosphor, heroicons, bootstrap, iconoir, ionicons, material, simpleicons, and mingcute."

First observedMay 5, 2026

TDQS

A3.9/5.0

Behavior1/5

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

Annotations set readOnlyHint to false, while the description describes 'Retrieve', implying a read-only operation. This is a direct annotation contradiction. No behavioral traits beyond the return value are disclosed, but the contradiction forces a score of 1.

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 three sentences, front-loaded with the primary purpose. Each sentence earns its place: the main action, a usage warning, and the return value. No wasted or redundant words.

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?

The description covers purpose, usage constraints (don't guess, use search_icons for concepts), and return value contents (SVG code, labels, preview URL, semantic guidance). An output schema exists, but the description adds valuable context without being bloated. Complete for a retrieval 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?

The input schema provides 100% parameter descriptions, establishing a baseline of 3. The description adds context that the id must be an exact ref from specific tools, but this is more usage guidance than parameter semantics. No additional syntax or format details are provided beyond the schema.

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?

Description clearly states 'Retrieve one exact SVG icon using an exact ref' with a specific verb and resource. It distinguishes from sibling tools by emphasizing 'exact' and requiring a ref from search_icons, recommend_icons, or preview_icons, contrasting with search and preview functions.

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?

Description explicitly instructs users to not guess icon IDs and to use search_icons first when the user only described a concept. This provides clear when-to-use guidance and an alternative tool recommendation.

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

All Supericons tools Inspect

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.

Get Icon

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources