Skip to main content
Glama

Search icons

search_icons
Read-only

Find icons by English keyword across Phosphor, Hugeicons, Feather, and Pixelarticons. Returns prefix:name matches; use get_icon to fetch the SVG.

Instructions

Searches Phosphor, Hugeicons, Feather and Pixelarticons (via Iconify, free). Returns names as prefix:name; use get_icon to get the SVG. Search in English (house, arrow, settings).

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
setsNoDefault: all
limitNo
queryYesSearch term in English

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark this read-only and open-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: results are names only, not SVGs, which tells the agent it must chain into get_icon. It does not mention pagination or how to widen results when a query underperforms, but no output schema exists to cover the return shape, so this disclosure carries real weight.

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?

Two tight sentences: sources and return format first, then the follow-up call and query-language rule. Every clause carries information an agent needs, with no filler.

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?

For a three-parameter, read-only search tool with no output schema, the description covers sources, result format, query language, and the next step. Missing only marginal details like result counts versus limit and behavior when no match is found.

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 67% and already documents sets (default all), limit (default 24, max 100) and query. The description only reinforces the query-language constraint (English, with examples), adding little about the sets or limit parameters beyond the schema. Baseline 3 is appropriate.

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 (searches) and resource (icons) plus the exact underlying sets (Phosphor, Hugeicons, Feather, Pixelarticons) and the return shape (prefix:name). It is clearly distinguishable from get_icon, which it names as the follow-up step.

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 gives a clear two-step workflow (search here, then call get_icon for the SVG) and a usage constraint that searches must be English terms with examples. It does not say when to prefer this over siblings like search_images or search_components, but the icon-specific scope makes that largely self-evident.

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