Skip to main content
Glama

Supericons

by io.github.curlymolelabs

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. Long icon lists 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

TableJSON Schema
NameRequiredDescriptionDefault
limitNoRequested inline icon count. Values outside 1 to 12 are safely clamped with a warning. Numeric strings are accepted.
queryNoOptional search query to preview visually, for example "license plate recognition camera scan car".
styleNoOptional style preference. Unsupported values are ignored with a warning.any
localeNoOptional 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.
libraryNoOptional 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_refsNoOptional 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.
include_imageNoWhen true, include a PNG contact sheet as MCP image content. Boolean strings are accepted. A preview_url is always returned.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoRecoverable error message when preview inputs are missing or invalid.
queryNoSearch query used for the visual preview, if any.
resultsYesIcons included in the visual preview.
warningsNoUnsupported optional inputs that were safely ignored.
image_urlNoDirect PNG URL for clients or Markdown renderers that can show remote images.
next_stepYesUseful next action for the caller.
preview_urlYesBrowser URL for visual inspection.
image_includedYesWhether this response includes MCP image content.
markdown_imageNoReady-made Markdown image snippet for final answers in clients that render remote Markdown images.
rendered_countYesNumber of icons rendered in the inline preview.
truncated_fromNoOriginal icon ref count when the input was truncated.
client_display_noteYesPlain-language note for clients that do not render images inline.
browser_preview_countYesNumber of accepted icon refs available at preview_url.
suggested_response_markdownNoReady-to-use answer with the image, refs, and browser fallback link.

TDQS

A4.5/5.0
Behavior4/5

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

Beyond read-only/idempotent annotations, the description discloses truncation behavior for long icon lists and outlines the return format (Markdown, hosted preview, PNG URL, optional MCP contact sheet), adding useful behavioral context.

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?

Three sentences front-load purpose, provide usage guidance, and summarize outputs without unnecessary 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?

With a rich schema and output schema, the description covers purpose, alternatives, and key behaviors, making it complete for an agent to select and invoke correctly.

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% with descriptive parameter details, so the description does not need to explain parameters. It adds a small amount of context by referencing icon_refs, but the schema already covers semantics.

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 a specific action ('Refine an icon result set or preview known icon refs') and resource ('icon refs returned by another Supericons tool'), distinguishing it from search_icons which is the primary request tool.

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?

Explicitly instructs to use search_icons first for normal icon requests, positioning this tool as a refinement/preview step. Also implies it works with refs from other Supericons tools, providing clear when-to-use context.

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

All Supericons toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct stage of the icon workflow: list_libraries for discovery, search_icons for concept search, recommend_icons for UI slot sets, preview_icons for refining/previewing results, and get_icon for exact retrieval. The descriptions explicitly state when to use each tool, so there is little risk of misselection.

Naming Consistency5/5

All tool names follow a consistent lowercase snake_case verb_noun pattern: list, search, preview, recommend, get. The object nouns are plural for set-level operations and singular for exact retrieval, which is predictable and clear.

Tool Count5/5

Five tools is well-scoped for an icon retrieval server. Each tool serves a necessary and non-redundant function, and the set is neither bloated nor too thin.

Completeness5/5

The tool surface covers the full icon workflow: library discovery, semantic search, preview/refinement, exact SVG retrieval, and multi-slot recommendation. No-result and insufficient-context cases are handled with next steps, so there are no obvious dead ends for the stated domain.

Resources