RemixIcon MCP

Official

by Remix-Design

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Search Remix Icons by keyword

search_icons

Search Remix Icon metadata using comma-separated keywords. Returns top 5 most relevant icons with names and scores.

Instructions

Search Remix Icon metadata using comma-separated keywords (up to 20 keywords). Returns top 5 most relevant icons. Supports both single keywords and keyword lists. Avoid natural language sentences. Returns format: 'icon-name (score)'. Example: 'sun-fill (46.00)'.

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

Input Schema

Name	Required	Description	Default
`keywords`	Yes	Comma-separated keywords to search for icons (e.g., 'summer, sun, beach')

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.2.0May 4, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedJan 26, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations, but description fully covers behavior: returns top 5 results, formatted output, keyword constraints. It implies read-only search, sufficient for the tool.

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 concise sentences, no redundant information, front-loaded with essential use case.

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?

Single parameter with full schema description, no output schema needed; description covers constraints, usage, and expected output format. Complete for the tool's complexity.

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 covers parameter description (100%), but description adds value: keyword limit, natural language avoidance, output format example. Adds meaning beyond schema.

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 the tool searches Remix Icon metadata using keywords, with specific verb 'search' and resource 'Remix Icon metadata'. It also details output format and constraints.

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?

Provides explicit guidance on using comma-separated keywords, limit of 20, avoiding natural language, and that it returns top 5 results. No need for exclusions due to lack of sibling tools.

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

Deploy Server

Other Tools

search_iconsA