Skip to main content
Glama
Sign In

Svg/icons MCP

by com.svgicons
OverviewDiscussionsAdmin

List Icon Collections

list_icon_collections
Read-only

List your persistent Icon Collections with icon counts. Requires a Pro API token with collections:read and mcp:use scopes.

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_collections"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOne-based page number. Default 1.
limitNoCollections per page, 1-50. Default 20.
queryNoOptional name or slug filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Collections per page, 1-50. Default 20."
    • addedInput schema / properties / page / description
      Added value: +"One-based page number. Default 1."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only provide readOnlyHint=true. The description adds non-obvious context: the collections are persistent, listing includes icon counts, and specific auth scopes (collections:read, mcp:use) are required. No contradiction with annotations.

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 concise sentences front-load the core purpose and output ('List your persistent Icon Collections with icon counts') before adding the essential auth requirement. Every word earns its place.

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 straightforward list operation with fully documented params, a readOnly annotation, and auth details, the description is largely complete. It could optionally describe the response structure beyond icon counts, but the provided information is sufficient for selection and invocation.

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% with clear descriptions for all three parameters (page, limit, query). The tool description adds no parameter-specific detail, so the baseline of 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?

The description uses a specific verb ('List') and resource ('persistent Icon Collections') and adds a distinctive output detail ('with icon counts'). It clearly distinguishes from singular get_icon_collection and other sibling search/add/export tools.

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?

It clearly states the prerequisite (Pro API token) and required scopes, which is helpful context. However, it does not explicitly explain when to prefer this over get_icon_collection or search_icons, nor does it mention any when-not-to-use cases.

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

All Svg/icons MCP toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources