Supericons

Preview Icons

preview_icons

Read-onlyIdempotent

Refine an icon result set or preview known icon refs returned by another Supericons tool. Use search_icons first for normal icon requests. Icon lists up to 100 refs are accepted and safely truncated to 12. Returns ready-to-use Markdown, a hosted preview fallback, a direct PNG image URL, and, when requested, an MCP image contact sheet.

Input Schema

Name	Required	Description	Default
`limit`	No	Requested inline icon count. Values outside 1 to 12 are safely clamped with a warning. Numeric strings are accepted.
`query`	No	Optional search query to preview visually, for example "license plate recognition camera scan car".
`style`	No	Optional style preference. Unsupported values are ignored with a warning.	any
`locale`	No	Optional locale for multilingual search terms. Supported values: zh-Hans, zh-Hant, ja, ko, es, de, pt, ar, hi, vi, th. Unsupported values are ignored with a warning.
`library`	No	Optional library key. 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.
`icon_refs`	No	Optional fixed icon refs in library:id format. Arrays, a single ref, and comma-separated refs are accepted. Up to 100 are accepted, 24 appear on the browser preview, and 12 are rendered inline. Send at most 100; very large arrays are refused.
`include_image`	No	When true, include a PNG contact sheet as MCP image content. Boolean strings are accepted. A preview_url is always returned.

Output Schema

Name	Required	Description
`error`	No	Recoverable error message when preview inputs are missing or invalid.
`query`	No	Search query used for the visual preview, if any.
`results`	Yes	Icons included in the visual preview.
`warnings`	No	Unsupported optional inputs that were safely ignored.
`image_url`	No	Direct PNG URL for clients or Markdown renderers that can show remote images.
`next_step`	Yes	Useful next action for the caller.
`preview_url`	Yes	Browser URL for visual inspection.
`image_included`	Yes	Whether this response includes MCP image content.
`markdown_image`	No	Ready-made Markdown image snippet for final answers in clients that render remote Markdown images.
`rendered_count`	Yes	Number of icons rendered in the inline preview.
`truncated_from`	No	Original icon ref count when the input was truncated.
`client_display_note`	Yes	Plain-language note for clients that do not render images inline.
`browser_preview_count`	Yes	Number of accepted icon refs available at preview_url.
`suggested_response_markdown`	No	Ready-to-use answer with the image, refs, and browser fallback link.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026

changedInput schema / properties / icon_refs / description

Previous value: -"Optional fixed icon refs in library:id format. Arrays, a single ref, and comma-separated refs are accepted. Up to 100 are accepted, 24 appear on the browser preview, and 12 are rendered inline. Larger lists are safely truncated with a warning."New value: +"Optional fixed icon refs in library:id format. Arrays, a single ref, and comma-separated refs are accepted. Up to 100 are accepted, 24 appear on the browser preview, and 12 are rendered inline. Send at most 100; very large arrays are refused."

Changed1 schema field changedJul 31, 2026

addedOutput schema / properties / suggested_response_markdown

Added value: +{
+  "description": "Ready-to-use answer with the image, refs, and browser fallback link.",
+  "type": "string"
+}

Changed24 schema fields changedJul 21, 2026

changedInput schema / properties / icon_refs / description

Previous value: -"Optional fixed icon refs in library:id format, for example [\"si:x-ai\", \"mingcute:scan_2_line\"]."New value: +"Optional fixed icon refs in library:id format. Arrays, a single ref, and comma-separated refs are accepted. Up to 100 are accepted, 24 appear on the browser preview, and 12 are rendered inline. Larger lists are safely truncated with a warning."

removedInput schema / properties / icon_refs / maxItems
```
Removed value: -12
```

changedInput schema / properties / include_image / description

Previous value: -"When true, include a PNG contact sheet as MCP image content. A preview_url is always returned."New value: +"When true, include a PNG contact sheet as MCP image content. Boolean strings are accepted. A preview_url is always returned."

addedInput schema / properties / library / $ref
```
Added value: +"#/properties/query"
```
removedInput schema / properties / library / type
```
Removed value: -"string"
```
changedInput schema / properties / limit / default
```
Previous value: -9New value: +12
```

changedInput schema / properties / limit / description

Previous value: -"Maximum icons to include in the preview. Keep this small for image-capable clients."New value: +"Requested inline icon count. Values outside 1 to 12 are safely clamped with a warning. Numeric strings are accepted."

removedInput schema / properties / limit / maximum
```
Removed value: -12
```
removedInput schema / properties / limit / minimum
```
Removed value: -1
```

changedInput schema / properties / limit / type

Previous value: -"number"New value: +[
+  "number",
+  "string"
+]

addedInput schema / properties / locale / $ref
```
Added value: +"#/properties/query"
```

changedInput schema / properties / locale / description

Previous value: -"Optional locale for multilingual search terms. Supported values: zh-Hans, zh-Hant, ja, ko, es, de, pt, ar, hi, vi, th."New value: +"Optional locale for multilingual search terms. Supported values: zh-Hans, zh-Hant, ja, ko, es, de, pt, ar, hi, vi, th. Unsupported values are ignored with a warning."

removedInput schema / properties / locale / enum

Removed value: -[
-  "zh-Hans",
-  "zh-Hant",
-  "ja",
-  "ko",
-  "es",
-  "de",
-  "pt",
-  "ar",
-  "hi",
-  "vi",
-  "th"
-]

removedInput schema / properties / locale / type
```
Removed value: -"string"
```
addedInput schema / properties / style / $ref
```
Added value: +"#/properties/query"
```

changedInput schema / properties / style / description

Previous value: -"Optional style preference."New value: +"Optional style preference. Unsupported values are ignored with a warning."

removedInput schema / properties / style / enum

Removed value: -[
-  "any",
-  "outline",
-  "solid"
-]

removedInput schema / properties / style / type
```
Removed value: -"string"
```

addedOutput schema / properties / browser_preview_count

Added value: +{
+  "description": "Number of accepted icon refs available at preview_url.",
+  "type": "number"
+}

addedOutput schema / properties / next_step

Added value: +{
+  "description": "Useful next action for the caller.",
+  "type": "string"
+}

addedOutput schema / properties / rendered_count

Added value: +{
+  "description": "Number of icons rendered in the inline preview.",
+  "type": "number"
+}

addedOutput schema / properties / truncated_from

Added value: +{
+  "description": "Original icon ref count when the input was truncated.",
+  "type": "number"
+}

addedOutput schema / properties / warnings

Added value: +{
+  "description": "Unsupported optional inputs that were safely ignored.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "preview_url",
-  "image_included",
-  "client_display_note",
-  "results"
-]New value: +[
+  "preview_url",
+  "image_included",
+  "rendered_count",
+  "browser_preview_count",
+  "next_step",
+  "client_display_note",
+  "results"
+]

Changed2 schema fields changedJul 3, 2026

addedOutput schema / properties / image_url

Added value: +{
+  "description": "Direct PNG URL for clients or Markdown renderers that can show remote images.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / markdown_image

Added value: +{
+  "description": "Ready-made Markdown image snippet for final answers in clients that render remote Markdown images.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

AddedJul 3, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the read-only/idempotent annotations, it discloses truncation behavior (100 accepted, 12 rendered inline), refusal of very large arrays, and the full output surface: Markdown, hosted preview fallback, direct PNG URL, and optional MCP image contact sheet. These are exactly the traits an agent needs before calling.

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?

Four tight sentences, front-loaded with purpose and routing before behavioral and return details. Slight duplication of the schema's truncation rules costs it a point, but nothing is wasted.

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?

With an output schema present, the description needn't explain return values yet does, and it covers annotations, truncation, and the sibling alternative. The one real gap is that it never says whether query and icon_refs can be combined or are mutually exclusive, which an agent must know for this seven-parameter 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 100%, so every parameter's meaning, defaults, and clamping rules are already documented structurally. The description restates the 100-to-12 truncation rather than adding new semantics, and leaves the interaction between query and icon_refs unexplained. Baseline 3 is appropriate.

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 two concrete modes: refining an existing icon result set, and previewing known icon refs produced by another Supericons tool. It explicitly names the sibling to use for the normal case, so an agent can choose between preview_icons and search_icons without opening either 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?

Gives an explicit routing rule ('Use search_icons first for normal icon requests') plus the condition that selects this tool (refining a result set or previewing known refs). No exclusions are needed because the alternative path is fully named.

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

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.