Skip to main content
Glama

Iconify List Collections

iconify_list_collections
Read-onlyIdempotent

Browse available icon collections. Returns prefix, name, icon count, author, license, and category. Use the prefix with search_icons or get_icons.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
totalYesTotal number of available collections
collectionsYesArray of collection metadata objects

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety and idempotency profile is fully covered without prose. The description's main added value is the workflow hint that the returned prefix feeds search_icons/get_icons; the field list is largely redundant with the existing output schema, and nothing is said about pagination or result size for a potentially large catalog.

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 compact sentences, front-loaded with purpose, then return shape, then the actionable next step; no filler. The middle sentence listing return fields is the one partially wasted element given the output schema exists.

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?

With zero parameters, full annotation coverage, and an output schema, the description covers purpose, returns, and the follow-up call. Minor omissions (result volume, whether the list is exhaustive) are low-risk for a small, well-defined catalog endpoint.

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?

The tool takes no parameters, so the 4 baseline applies and there is no schema semantics left to explain. The description does usefully define what a 'prefix' is in this ecosystem, which is the implicit input to sibling tools.

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?

States a specific verb and resource ('Browse available icon collections') and immediately enumerates the returned fields (prefix, name, icon count, author, license, category), so the agent knows exactly what this yields. It also distinguishes itself from search_icons and get_icons by positioning itself as the source of the prefix those tools consume.

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?

The sentence 'Use the prefix with search_icons or get_icons' gives explicit downstream chaining guidance and names the relevant siblings, which is the key usage decision for a zero-parameter listing tool. It stops short of an explicit when-not-to-use statement, but for an entry-point catalog call there is little else an agent needs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.