infyicon-mcp

Get SVG for several icons

get_icon_svg_bulk

Read-onlyIdempotent

Fetch ready-to-embed SVG markup for up to 20 Infyicon icons in a single call, ideal for building UI icon sets or design systems.

Instructions

Return ready-to-embed SVG markup for 1-20 Infyicon icons in one call (pass an array of ids from search_icons). Use when building a UI, icon set or design system so you fetch several icons at once instead of calling get_icon_svg repeatedly; use get_icon_svg for a single icon. Read-only, no auth; ids beyond the first 20 are silently dropped; each bad or unknown id gets a per-item error while the rest still succeed; oversized SVGs (>200 KB) return svg_url instead of markup. Free with attribution to infyicon.com.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ids": "<ids>"
    },
    "name": "get_icon_svg_bulk"
  }
}

Input Schema

Name	Required	Description	Default
`ids`	Yes	Array of 1-20 icon ids, e.g. ["home-2_101", "gear-1_202"]

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.2.1Sep 23, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Discloses multiple non-obvious behaviors beyond annotations: ids beyond 20 are silently dropped, per-item errors with partial success, oversized SVGs return svg_url instead of markup, and attribution requirement. No contradiction with readOnly/idempotent 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?

Four sentences pack purpose, usage, limits, error handling, and return behavior without repetition. Front-loaded with the main result, keeping the call condition first.

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 read-only bulk fetch with no output schema, it covers the request parameters, behavior limits, error semantics, fallback return, and licensing. An agent has enough to invoke and interpret results correctly.

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 already documents the ids array with min/max and example (100% coverage), so baseline is 3. Description adds meaningful usage semantics: ids should come from search_icons, the 20-item cap behavior, and partial-error handling, which improves correctness.

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 + resource ('Return ready-to-embed SVG markup for 1-20 Infyicon icons in one call') and explicitly differentiates from get_icon_svg for single icons. The bulk behavior is unambiguous.

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?

Explicitly says when to use: 'when building a UI, icon set or design system' and when to use alternative: 'use get_icon_svg for a single icon'. Also tells where ids come from: 'array of ids from search_icons'. This is above and beyond.

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

Deploy Server