Skip to main content
Glama

list_icons

List available icons for diagram creation, filtered by provider (e.g., gcp, k8s) and service (e.g., compute, database). Discover providers, services, and icons hierarchically.

Instructions

List available icons from the diagrams package, with optional filtering.

This tool dynamically inspects the diagrams package to find available providers, services, and icons that can be used in diagrams.

USAGE INSTRUCTIONS:

  1. Call without filters to get a list of available providers

  2. Call with provider_filter to get all services and icons for that provider

  3. Call with both provider_filter and service_filter to get icons for a specific service

Example workflow:

  • First call: list_icons() → Returns all available providers

  • Second call: list_icons(provider_filter="gcp") → Returns all GCP services and icons

  • Third call: list_icons(provider_filter="gcp", service_filter="compute") → Returns GCP compute icons

This approach is more efficient than loading all icons at once, especially when you only need icons from specific providers or services.

Returns: Dictionary with available providers, services, and icons organized hierarchically

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
service_filterNoFilter icons by service name (e.g., "compute", "database", "network", "analytics", "ml", "storage")
provider_filterNoFilter icons by provider name (e.g., "gcp", "k8s", "onprem", "saas")
Behavior4/5

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

No annotations provided, but description explains it dynamically inspects the package and returns a hierarchical dictionary. Could mention performance considerations but otherwise transparent for a read-only inspection tool.

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?

Well-structured with clear sections (description, usage instructions, example workflow, returns). Every sentence is informative. No fluff.

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?

Even without an output schema, the description explains the return structure (dictionary with providers, services, icons hierarchically). Covers all essential information for correct use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with concise descriptions. The description adds significant value by explaining the progressive filtering pattern and giving concrete examples of parameter values ("gcp", "compute").

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 clearly states it lists available icons from the diagrams package with optional filtering. It distinguishes from sibling tools (generate_diagram, get_diagram_examples) by focusing on icon discovery.

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

Usage Guidelines5/5

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

Provides detailed step-by-step usage instructions with examples, including the progressive filtering workflow. Tells the agent when to call with no filters, with provider_filter, and with both filters.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lesonky/gcp-diagrams-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server