Supericons

List Libraries

list_libraries

Read-onlyIdempotent

List the free icon libraries available through the hosted Supericons MCP server. Use this before filtering by library or when a user asks which icon libraries are supported.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`libraries`	Yes	Free icon libraries available through this hosted MCP server.
`publicRecordCount`	Yes	Number of public semantic icon records searchable through the hosted MCP server.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedJul 15, 2026

addedOutput schema / properties / libraries / items / properties / outlineCount

Added value: +{
+  "description": "Number of outline icons served by the hosted MCP server.",
+  "type": "number"
+}

addedOutput schema / properties / libraries / items / properties / solidCount

Added value: +{
+  "description": "Number of solid icons served by the hosted MCP server.",
+  "type": "number"
+}

addedOutput schema / properties / libraries / items / properties / supportedStyles

Added value: +{
+  "description": "Styles verified on the hosted serving path.",
+  "items": {
+    "enum": [
+      "outline",
+      "solid"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / properties / libraries / items / required

Previous value: -[
-  "id",
-  "name",
-  "description",
-  "count"
-]New value: +[
+  "id",
+  "name",
+  "description",
+  "count",
+  "outlineCount",
+  "solidCount",
+  "supportedStyles"
+]

Changed1 schema field changedJul 3, 2026

addedOutput schema / properties / libraries / items / properties / label

Added value: +{
+  "description": "Human-readable library label with key, for example Supericons (si).",
+  "type": "string"
+}

Changed2 schema fields changedJun 27, 2026

addedOutput schema / properties / libraries / items / properties / count

Added value: +{
+  "description": "Number of icons in the library.",
+  "type": "number"
+}

changedOutput schema / properties / libraries / items / required

Previous value: -[
-  "id",
-  "name",
-  "description"
-]New value: +[
+  "id",
+  "name",
+  "description",
+  "count"
+]

Changed2 schema fields changedMay 4, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "libraries": {
+      "description": "Free icon libraries available through this hosted MCP server.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "description": {
+            "description": "Brief public description of the icon library.",
+            "type": "string"
+          },
+          "id": {
+            "description": "Library key used in tool calls.",
+            "type": "string"
+          },
+          "name": {
+            "description": "Human-readable library name.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "description"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "publicRecordCount": {
+      "description": "Number of public semantic icon records searchable through the hosted MCP server.",
+      "type": "number"
+    }
+  },
+  "required": [
+    "libraries",
+    "publicRecordCount"
+  ],
+  "type": "object"
+}

First observedMay 3, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the 'free' scope and hosted-server context, but discloses no additional behaviors like pagination or rate limits. This is sufficient for a simple list operation.

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: the first states the purpose clearly, the second gives a usage tip. No filler or redundant information.

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 zero parameters, rich annotations, and the presence of an output schema, the description fully covers what an agent needs to select and invoke the tool correctly.

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?

There are zero parameters, so the baseline is 4. The description adds relevant context about the list's content ('free icon libraries') without needing to describe any parameter syntax.

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' with a clear resource 'free icon libraries' and context ('hosted Supericons MCP server'). It distinguishes from sibling tools that operate on individual icons, making the tool's purpose unambiguous.

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?

It explicitly advises use before filtering by library and when users ask about supported libraries. This provides clear context, though it does not name alternative tools directly or specify when not to use it.

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

All Supericons tools Inspect

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

Need Help?