Skip to main content
Glama

Supericons

by io.github.curlymolelabs

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
NameRequiredDescriptionDefault
limitNoMaximum number of icons from 1 to 50. Numeric strings are accepted.
queryYesIcon concept or search phrase, for example "database", "user profile", "chill", "trash", "upload cloud", "AI model", or "beautiful".
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 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_modeNoOptional 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_frameNoOptional public-safe diagnostics for query understanding. Boolean strings are accepted. Leave false for normal compact responses.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoStable code for a structured no-result.
hintNoPlain-language recovery hint for a structured no-result.
errorNoPlain-language error for a structured no-result.
statusNoHTTP status from an upstream search failure.
detailsNoStructured rate-limit or upstream failure details.
resultsYesMatching icons with SVG code and semantic guidance.
warningsNoUnsupported optional inputs that were safely ignored.
image_urlNoDirect PNG URL when usable icons exist.
next_stepYesUseful next action for the caller.
retryableNoWhether changing the query or filters may produce a result.
limit_scopeNoAllowance scope reported by a rate limit.
preview_urlNoBrowser URL for visual inspection of this search result set.
query_frameNoOptional public-safe query understanding diagnostics.
library_modeYesLibrary behavior used for this search.
outcome_typeNoWhether this response contains results, an honest no-match, or a tool failure.
result_countNoNumber of verified icons returned by this search.
markdown_imageNoReady-made Markdown image when usable icons exist.
search_runtimeNoSearch execution path used for this request.
top_result_refNoTop ordered icon ref when results exist.
requested_libraryYesPreferred or required library, when supplied.
retry_after_secondsNoSeconds to wait before retrying a rate-limited search.
result_interpretationNoPlain-language guidance for interpreting this result count and outcome.
suggested_response_markdownYesCompact 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?

Annotations are all false, so the description carries the full behavioral burden. It thoroughly discloses match behavior (paste-ready answer, direct preview image, Markdown), no-match behavior (honest structured no-result with next step, no fabricated icon), and library-mode semantics. The si/Supericons disambiguation also prevents a likely misuse. This exceeds the minimum expected transparency.

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: the primary-role statement, search capability, match/no-match response behavior, library-mode guidance, and the si/Supericons warning. It is front-loaded with the most important usage directive and remains compact for a tool with 7 parameters.

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 is complete for correct invocation: it covers query style, result behavior, failure handling, library selection, and a known naming trap. The output schema exists, so detailed return-value documentation is already available to the agent. No critical operational context is missing.

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 coverage is 100%, so the baseline is 3. The description adds meaningful guidance beyond the schema by explaining the prefer/strict library_mode behavior, the condition for strict usage, and the si key ambiguity. This additional context raises the score.

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 opens with 'Use this as the main icon tool' and names a specific action and resource: searching 20,000+ curated SVG icons across 11 libraries by meaning, labels, visual description, tags, and synonyms. It clearly establishes this as the primary search tool and distinguishes it from siblings like get_icon and list_libraries.

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?

The description gives explicit guidance on when to use this tool ('main icon tool') and how to choose library modes: 'If you choose a library yourself, use prefer' and 'Use strict only when the user explicitly requires that library.' It does not explicitly compare against sibling tools, but the primary-tool framing and mode rules provide clear usable 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