Skip to main content
Glama
SVGForge MCP

SVGForge MCP

by liqiang88

search_icons

Search Iconify icons by keyword to retrieve icon keys and brief metadata, with optional prefix filtering to narrow results.

Instructions

Search SVGForge / Iconify icons by keyword. Returns icon keys (prefix:name) and brief meta. Prefer a prefix (e.g. lucide) for faster results.

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

Input Schema

NameRequiredDescriptionDefault
qYesSearch keyword, e.g. home, arrow, user
limitNoMax results (default 20, max 50)
prefixNoOptional icon set prefix filter, e.g. lucide, tabler, mdi

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the return format and a performance tradeoff for prefix filtering. It says nothing about permissions, rate limits, or result ordering/relevance behavior, which leaves meaningful gaps for an unannotated tool.

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?

Three short sentences, front-loaded with the core action and return value, with zero filler. Slightly terse given it is the only behavioral documentation available.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A read-only search tool with a fully described schema and no output schema needs little, and the description covers action, output, and a filter tip. It still omits matching/pagination semantics and any relationship to sibling retrieval tools, leaving it adequate but not complete.

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 q, limit, and prefix are already documented, establishing a baseline of 3. The line about preferring a prefix adds a genuine performance rationale beyond the schema, but no detail on matching semantics (substring vs fuzzy) or how prefix combines with q.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Search SVGForge / Iconify icons by keyword") and even names the return shape (icon keys prefix:name plus meta). It does not explicitly distinguish itself from siblings like list_icon_sets or get_icon, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Offers one actionable tip ("Prefer a prefix (e.g. lucide) for faster results") but gives no guidance on when to search versus calling get_icon directly or browsing via list_icon_sets. Usage is implied rather than stated against alternatives.

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