Supericons

Search Icons

search_icons

Use this as the main icon tool. Search 20,000+ curated SVG icons across 11 libraries by meaning, label, visual description, tags, and synonyms. When matches exist, the response includes a paste-ready suggested answer, a direct preview image, and Markdown that can show the image in the final reply. When no supported match exists, it returns an honest structured no-result with a next step and no fabricated icon. If you choose a library yourself, use prefer. Use strict only when the user explicitly requires that library. Library key si means Supericons, not Simple Icons.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of icons from 1 to 50. Numeric strings are accepted.
`query`	Yes	Icon concept or search phrase, for example "database", "user profile", "chill", "trash", "upload cloud", "AI model", or "beautiful".
`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 only when the user named a library. Omit it to search all libraries. Do not use all as a 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.
`library_mode`	No	Optional library behavior. Omit a self-chosen library and search all, or use prefer with that library. Use strict only when the user explicitly requires the named library. All searches every eligible library. Unsupported or incomplete combinations are safely normalized with a warning.
`include_query_frame`	No	Optional public-safe diagnostics for query understanding. Boolean strings are accepted. Leave false for normal compact responses.

Output Schema

TableJSON Schema

Name	Required	Description
`code`	No	Stable code for a structured no-result.
`hint`	No	Plain-language recovery hint for a structured no-result.
`error`	No	Plain-language error for a structured no-result.
`status`	No	HTTP status from an upstream search failure.
`details`	No	Structured rate-limit or upstream failure details.
`results`	Yes	Matching icons with SVG code and semantic guidance.
`warnings`	No	Unsupported optional inputs that were safely ignored.
`image_url`	No	Direct PNG URL when usable icons exist.
`next_step`	Yes	Useful next action for the caller.
`retryable`	No	Whether changing the query or filters may produce a result.
`limit_scope`	No	Allowance scope reported by a rate limit.
`preview_url`	No	Browser URL for visual inspection of this search result set.
`query_frame`	No	Optional public-safe query understanding diagnostics.
`library_mode`	Yes	Library behavior used for this search.
`outcome_type`	No	Whether this response contains results, an honest no-match, or a tool failure.
`result_count`	No	Number of verified icons returned by this search.
`markdown_image`	No	Ready-made Markdown image when usable icons exist.
`search_runtime`	No	Search execution path used for this request.
`top_result_ref`	No	Top ordered icon ref when results exist.
`requested_library`	Yes	Preferred or required library, when supplied.
`retry_after_seconds`	No	Seconds to wait before retrying a rate-limited search.
`result_interpretation`	No	Plain-language guidance for interpreting this result count and outcome.
`suggested_response_markdown`	Yes	Compact answer that accurately reflects this response.

TDQS

A4.7/5.0

Behavior5/5

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

All annotations are false, so the description carries the full behavioral burden. It discloses the success response shape (paste-ready suggested answer, preview image, Markdown), the no-result behavior (honest structured no-result with a next step and no fabricated icon), and the si key ambiguity. This is rich, non-obvious behavioral context beyond the schema.

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?

Every sentence earns its place: main-tool purpose, search semantics, success response, failure behavior, and library-mode rules. The most important information is front-loaded, and the description is dense without being bloated.

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 an output schema present, 100% schema coverage, and rich annotations-free behavioral disclosure, the description covers everything an agent needs to select and invoke the tool correctly. It explains query flexibility, result behavior, failure handling, and parameter selection rules with no major gaps.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful value for the trickiest parameter guidance: prefer versus strict, and the warning that si means Supericons, not Simple Icons. It does not need to repeat what the schema already documents.

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 opens by positioning itself as 'the main icon tool' and then gives a specific verb and resource: search 20,000+ curated SVG icons across 11 libraries by meaning, label, visual description, tags, and synonyms. This clearly distinguishes it from sibling tools like get_icon, preview_icons, and recommend_icons.

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?

It explicitly says to use this as the main icon tool and gives precise conditional guidance: use prefer when the agent chooses a library, and use strict only when the user explicitly requires that library. It does not name sibling alternatives or say when to choose them instead, so it falls just short of a 5.

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?