Skip to main content
Glama
Sign In

All SVG Icons

by com.allsvgicons
OverviewDiscussionsAdmin

Search icons

search_icons
Read-only

Searches SVG icons and brand logos by keyword. Use this when the user asks to find an icon or logo. Returns matching icon identifiers in "prefix:name" format and does not return SVG content. To save many icons as files, download https://i.allsvgicons.com//.svg directly instead of calling get_icon for each one. Where supported, it also displays an icon grid.

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": {
      "query": "<query>"
    },
    "name": "search_icons"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results to return, up to 20
queryYesKeyword or phrase describing the requested icon
pickerNoWhether to show the icon grid when the client supports it (default true). Pass false for searches the user does not need to see
prefixNoLimit the search to one icon set prefix, such as "mdi"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max results, capped at 20"New value: +"Number of results to return, up to 20"
    • changedInput schema / properties / picker / description
      Previous value: -"Show the icon grid to the user (default true). Pass false for searches the user does not need to see"New value: +"Whether to show the icon grid when the client supports it (default true). Pass false for searches the user does not need to see"
    • changedInput schema / properties / prefix / description
      Previous value: -"Scope the search to a single icon set prefix, e.g. \"mdi\""New value: +"Limit the search to one icon set prefix, such as \"mdi\""
    • changedInput schema / properties / query / description
      Previous value: -"Search keyword"New value: +"Keyword or phrase describing the requested icon"
  2. Changed1 schema field changed
    • addedInput schema / properties / picker
      Added value: +{
+  "description": "Show the icon grid to the user (default true). Pass false for searches the user does not need to see",
+  "type": "boolean"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover read-only/non-destructive safety, and the description adds substantive context: return format ('prefix:name'), explicit exclusion of SVG content, the direct download URL pattern, and the conditional icon-grid display. This is meaningful disclosure beyond the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads purpose and trigger, then adds return format and the download tip; each sentence earns its place. Slightly dense in the third sentence but no real waste.

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 usefully explains the return value and that no SVG payload comes back, and covers the bulk-download workflow. The remaining gap is not clarifying the overlap with find_brand_logo for logo-specific searches.

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 coverage is 100%, so all four parameters are already documented, including the picker default and limit cap. The description adds only implicit color (grid display relates to picker), so baseline 3 applies.

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 and resource ('Searches SVG icons and brand logos by keyword') and clarifies output form ('prefix:name' identifiers, no SVG content), which distinguishes it from get_icon (which presumably returns SVG) and from find_brand_logo's narrower scope.

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?

Gives a clear trigger ('when the user asks to find an icon or logo') and an explicit alternative path for bulk downloads instead of looping get_icon. However, it doesn't clarify when to prefer this over the sibling find_brand_logo, despite both covering logos.

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

All All SVG Icons toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources