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. 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

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. Larger lists are safely truncated with a warning.
`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

TableJSON 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.

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral context beyond annotations: 'Long icon lists are accepted and safely truncated to 12' and the return format (Markdown, hosted preview fallback, direct PNG URL, MCP contact sheet). No contradiction found.

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: purpose first, usage guidance second, and behavioral detail third. Every sentence earns its place, with no verbosity or redundancy. It is highly concise and well-structured.

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 the tool's complexity (7 optional parameters) and 100% schema coverage, the description covers purpose, usage, and key behavioral traits. It could be more explicit about how the 'query' parameter can be used independently, but the schema fills that gap. Overall, the description is sufficiently complete for an agent to understand when and how to use the 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%, with all 7 parameters having descriptions. The tool description does not add significant parameter-specific meaning beyond what the schema already provides. It mentions truncation to 12, but the schema already documents limit and icon_refs behavior, so 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?

The description clearly states a specific verb and resource: 'Refine an icon result set or preview known icon refs.' It also distinguishes from siblings by explicitly saying 'Use search_icons first for normal icon requests,' which positions this tool as a post-processing step.

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?

The description gives direct guidance: 'Use search_icons first for normal icon requests' and implies this tool is for refining/previewing results from other Supericons tools. This explicitly names an alternative and sets clear context for when to use this tool.

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

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.8/5.0

Disambiguation5/5

Each tool has a clearly distinct role: search finds icons, recommend builds sets for UI slots, preview refines result sets, get retrieves exact SVG code, and list_libraries enumerates available libraries. Despite some overlapping concepts like 'preview' and 'get', the descriptions explicitly differentiate when to use each one.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: list_libraries, search_icons, recommend_icons, preview_icons, get_icon. The naming style is uniform and predictable across the entire set.

Tool Count5/5

Five tools is well-scoped for an icon service: library discovery, search, recommendation, preview, and exact retrieval. Each tool addresses a necessary part of the icon selection workflow without unnecessary bloat.

Completeness5/5

The tool surface covers the full icon workflow: discover libraries, search by meaning, get multi-icon recommendations, preview sets in Markdown/PNG, and fetch exact SVG code. There are no obvious missing operations for the stated purpose.

Resources

Need Help?