Skip to main content
Glama

Supericons

by io.github.curlymolelabs

Get Icon

get_icon

Retrieve one exact SVG icon using an exact ref returned by search_icons, recommend_icons, or preview_icons. Do not guess icon IDs. Use search_icons first if the user only described a concept. Returns SVG code, explicit public library labels, visual preview URL, and public semantic guidance for the exact icon.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesExact icon ID without the library prefix, for example "database", "user-circle", "brain-circuit", or "arrow-down".
styleNoOptional style preference. Material Symbols supports outline and solid. Other hosted libraries report their verified styles in list_libraries.any
libraryYesRequired library key for the exact icon. 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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoStable error code when the exact icon is unavailable.
hintNoPlain-language explanation of how to recover.
iconNoExact matching icon when found.
errorNoRecoverable error message when no exact icon is found.
next_stepNoRecommended next tool action.
retryableNoWhether repeating the same exact lookup may succeed.

TDQS

A3.9/5.0
Behavior1/5

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

Annotations set readOnlyHint to false, while the description describes 'Retrieve', implying a read-only operation. This is a direct annotation contradiction. No behavioral traits beyond the return value are disclosed, but the contradiction forces a score of 1.

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, front-loaded with the primary purpose. Each sentence earns its place: the main action, a usage warning, and the return value. No wasted or redundant words.

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 covers purpose, usage constraints (don't guess, use search_icons for concepts), and return value contents (SVG code, labels, preview URL, semantic guidance). An output schema exists, but the description adds valuable context without being bloated. Complete for a retrieval 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?

The input schema provides 100% parameter descriptions, establishing a baseline of 3. The description adds context that the id must be an exact ref from specific tools, but this is more usage guidance than parameter semantics. No additional syntax or format details are provided beyond the schema.

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 clearly states 'Retrieve one exact SVG icon using an exact ref' with a specific verb and resource. It distinguishes from sibling tools by emphasizing 'exact' and requiring a ref from search_icons, recommend_icons, or preview_icons, contrasting with search and preview functions.

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?

Description explicitly instructs users to not guess icon IDs and to use search_icons first when the user only described a concept. This provides clear when-to-use guidance and an alternative tool recommendation.

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