Skip to main content
Glama
SVGForge MCP

SVGForge MCP

by liqiang88

list_icon_sets

List available SVG icon packs such as Lucide and Tabler so you can pick the right set. Filter results by prefix or name and cap how many sets return.

Instructions

List available SVGForge icon packs (Lucide, Tabler, etc.).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_icon_sets"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoOptional filter on prefix or name
limitNoMax sets to return (default 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'List' implies a safe read-only enumeration, but it says nothing about result truncation (the schema caps at 50 by default / 200 max), ordering, or pagination — meaningful gaps for an agent that may not inspect the schema.

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?

A single front-loaded sentence with zero filler; the resource being listed is named first and the examples are parenthetical. Nothing could be removed without losing information.

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?

For a zero-required-param, read-only enumeration tool this covers the core purpose, but with no output schema the description should hint at what a returned pack record contains. It also omits any note on result limits, leaving those details entirely to the schema.

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 description coverage is 100%, so both parameters (q, limit) are already documented with their semantics and default. The description adds no extra meaning about filtering behavior or what happens when q matches nothing, so baseline 3 applies.

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 ('List') and resource ('SVGForge icon packs') and even names concrete examples (Lucide, Tabler), so an agent knows this enumerates icon-pack collections rather than individual icons. It is clearly distinct from siblings like search_icons or get_icon, though it never explicitly contrasts itself with them.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no stated prerequisites, and no routing to alternatives such as search_icons or get_custom_icons. An agent can only infer from the verb that this is a discovery call, with nothing about ordering relative to other tools.

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