Skip to main content
Glama

infyicon-mcp

by io.github.krupalghori44-dev

search_icons

Search 161,000+ free Infyicon vector icons. Returns matches with icon id, style, page URL, SVG and PNG URLs. Styles: outline (black line), fill (black solid), color-outline, color-fill. Free to use with attribution to infyicon.com.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 10)
queryYesWhat to search for, e.g. "shopping cart", "doctor", "hammer"
styleNoOptional: restrict to one style
offsetNoOptional: skip this many results for pagination. Use next_offset from a previous call to get the next page.

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the disclosure burden. It proactively discloses return contents, style options, and licensing terms, but does not mention pagination behavior or next_offset usage.

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 dense sentences communicate purpose, scale, return fields, style variants, and licensing. Every sentence earns its place with no redundancy.

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?

With no output schema, the description adequately explains the main result contents and style options. It omits pagination details, though the offset parameter schema partially covers that.

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 description coverage is 100%, so the schema already documents all parameters with descriptions and examples. The description adds stylistic and output context but does not substantially deepen parameter-level understanding.

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?

States a specific verb (Search), a concrete resource (161,000+ Infyicon vector icons), and the returned fields. This clearly differentiates it from sibling tools like get_icon_svg, popular_icons, and related_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?

The description clearly establishes the use case: keyword search for icon assets. It does not explicitly name alternative tools or state when not to use this tool, but the context is unambiguous.

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

All infyicon-mcp 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/5.0
Disambiguation4/5

Most tools have clear, distinct roles: search, list categories, and fetch SVG/PNG by id. Some overlap exists because search_icons already returns SVG and PNG URLs, but get_icon_svg/get_icon_png are clearly meant for direct retrieval by known id.

Naming Consistency4/5

The naming pattern is generally consistent using verb_noun style: get_icon_svg, get_icon_png, list_categories, search_icons. uicons_lookup deviates slightly by starting with a product name instead of a verb, but it is still understandable and similar in spirit.

Tool Count5/5

Five tools is a well-scoped size for an icon service: search, browse categories, retrieve two format types, and check webfont usage. Each tool has a clear purpose and none feel redundant enough to remove.

Completeness4/5

The core icon workflow is covered: search, category discovery, SVG/PNG retrieval, and UI-font lookup. Minor gaps exist around category-specific icon listing or richer metadata, but agents can successfully search and fetch icons end-to-end.

Resources