Skip to main content
Glama
ViGi-P

lucide-mcp

by ViGi-P
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Search Icons

search-icons
Read-onlyIdempotent

Search for Lucide icons by submitting groups of related keywords. Each group returns a list of matching icon names.

Instructions

Use this to search for a list of Lucide icons using tokenised matching. Each tool call should receive an array of sub-arrays of keywords as input to use in the search. Each sub-array should contain related keywords that convey a specific concept or visual meaning. Avoid the use of articles (e.g. 'a', 'the') and prepositions (e.g. 'in', 'on') in keywords if possible. The tool will return an array of sub-arrays of icon names such that each output sub-array contains icon names that match the search criteria for that specific input sub-array. Then, from the list of matches, select the most appropriate icon name.

Usage Example: To search for icons that represents the concepts "home page", "graph" and "warning", you might call:

search-icons({ keywords: [["home", "house"], ["graph", "chart"], ["danger"]] })

This will return an output similar to:

{
  "matches": [
    [ "birdhouse", "house-heart", "house-plug", "house-plus", "house-wifi", "house", "map-pin-house" ],
    [ "chart-area", "chart-bar-big", "chart-bar-decreasing", "chart-bar-increasing", "chart-bar-stacked", "chart-bar", "chart-candlestick" ],
    [ "book-alert", "circle-alert", "cloud-alert", "file-exclamation-point", "message-circle-warning", "message-square-warning", "octagon-alert", "skull", "triangle-alert" ]
  ]
}

How to use icon names in code:

  • With React: Convert the selected icon name to Pascal-case and import as a component from the 'lucide-react' package.

  • With React Native: Convert the selected icon name to Pascal-case and import as a component from the 'lucide-react-native' package.

  • With Astro: Convert the selected icon name to Pascal-case and import as a component from the '@lucide/astro' package.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordsYesArray of sub-arrays of keywords to use in the search.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
matchesYesArray of sub-arrays of best-matching icon names.

Tool Definition Quality

A5/5.0
Behavior5/5

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

Annotations already indicate readOnly, idempotent, non-destructive. The description goes beyond by explaining tokenised matching, the return structure (array of sub-arrays), and how to convert results to code, adding valuable behavioral context.

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 well-structured: a clear purpose sentence, followed by instructions, an example, and framework-specific notes. No redundant sentences; every part earns its place.

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?

Given the presence of an output schema, the description explains the return format and usage. It covers input, output, and code integration completely, leaving no gaps.

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?

Schema coverage is 100%, but the description adds significant meaning: it explains that each sub-array should contain related keywords conveying a specific concept, and provides an example. This enriches the parameter understanding beyond the schema's generic description.

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 clearly states 'Use this to search for a list of Lucide icons using tokenised matching,' specifying the verb (search) and resource (Lucide icons). It is unambiguous and distinct from any siblings.

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 provides explicit guidance on when to use (searching icons), how to structure keywords (sub-arrays of related keywords, avoid articles/prepositions), and includes a detailed example and framework-specific usage instructions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ViGi-P/lucide-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server