Skip to main content
Glama

infyicon-mcp

by io.github.krupalghori44-dev
OverviewDiscussionsAdmin

Search icons

search_icons
Read-onlyIdempotent

Search 161,000+ free Infyicon vector icons by keyword and return up to 30 matches per page, each with icon id (slug_number), name, style, page URL, direct SVG URL, 512px PNG URL and tags. Styles: outline (black line), fill (black solid), color-outline, color-fill. Use this first whenever the user describes what icon they want; then pass an id to get_icon_svg, get_icon_svg_bulk or get_icon_png. Use get_popular_icons instead when there is no search term, and search_uicons instead when the user wants a CSS webfont class rather than an SVG/PNG file. Read-only, no auth, no API key; empty query returns an error; total_matches + next_offset are returned for paging. Free with attribution to infyicon.com.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results per page (default 10, max 30)
queryYesWhat to search for, e.g. "shopping cart", "doctor", "hammer" (1-4 plain words work best)
styleNoOptional: restrict to one style; omit to get all four styles mixed
offsetNoOptional: skip this many results for pagination. Pass next_offset from the previous response to get the next page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max results (default 10)"New value: +"Max results per page (default 10, max 30)"
    • changedInput schema / properties / offset / description
      Previous value: -"Optional: skip this many results for pagination. Use next_offset from a previous call to get the next page."New value: +"Optional: skip this many results for pagination. Pass next_offset from the previous response to get the next page."
    • changedInput schema / properties / query / description
      Previous value: -"What to search for, e.g. \"shopping cart\", \"doctor\", \"hammer\""New value: +"What to search for, e.g. \"shopping cart\", \"doctor\", \"hammer\" (1-4 plain words work best)"
    • changedInput schema / properties / style / description
      Previous value: -"Optional: restrict to one style"New value: +"Optional: restrict to one style; omit to get all four styles mixed"
  2. Changed1 schema field changed
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Optional: skip this many results for pagination. Use next_offset from a previous call to get the next page.",
+  "minimum": 0,
+  "type": "integer"
+}
  3. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations already mark the tool read-only, idempotent, and non-destructive, but the description adds substantial behavioral context: no auth or API key required, empty queries return an error, pagination via total_matches and next_offset, and free-with-attribution policy. No contradictions with annotations.

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 dense but every sentence carries distinct value: core behavior, return fields, style meanings, usage routing, and operational caveats. The most important information is front-loaded, and no sentences are filler.

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?

For a search tool with four parameters, no output schema, and several siblings, the description provides everything needed to invoke it correctly and interpret the result: result fields, style options, pagination signals, error behavior, and routing to downstream tools. Nothing critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema already covers all four parameters at 100%, the description enriches them: it explains the four style values in plain terms, notes that query works best with 1-4 plain words, gives concrete examples, and clarifies that offset should be fed from next_offset. This is meaningfully more than the schema alone provides.

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 with a specific verb and resource: 'Search 161,000+ free Infyicon vector icons by keyword'. It states exactly what is returned (icon id, name, style, URLs, tags), clearly distinguishing this search tool from related retrieval and listing tools.

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 explicit routing guidance: use this first whenever the user describes an icon, pass an id to get_icon_svg/get_icon_svg_bulk/get_icon_png afterward, use get_popular_icons when there is no search term, and use search_uicons when a CSS webfont class is wanted. This leaves no ambiguity about when to choose this tool.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources