Skip to main content
Glama

Get several icons as code

get_icons
Read-only

Up to 30 icons in one style and format in one call: the way to fetch every icon a screen needs once you have picked them.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "names": "<names>"
    },
    "name": "get_icons"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYes
styleNoline-round
formatNosvg

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the batch constraint of up to 30 icons in one style and format, but does not describe response shape, behavior for invalid names, or format/style implications.

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?

The definition is a single front-loaded sentence with no wasted exposition. The second clause is useful workflow context, though slightly marketing-like in phrasing. It is appropriately sized for a simple batch read tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has three parameters, two enums, no output schema, and 0% schema description coverage. The description covers the batch limit and homogeneous style/format requirement but leaves the enum meanings, defaults, and identifier expectations undocumented, which is a meaningful gap for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain the three parameters. It mentions the 30-icon cap and that one style and format apply per call, but it does not explain what 'names' should contain or what the style and format enum values mean, including defaults.

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?

The description states a specific batch-fetch purpose: retrieving up to 30 icons in one call, in a single style and format. The plural scope and 'every icon a screen needs' implicitly distinguish it from singular get_icon, though no sibling is named explicitly.

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 phrase 'once you have picked them' clearly positions this as a follow-up to icon selection, likely after search_icons. It also establishes the batch use case for a whole screen. It does not explicitly say when to use get_icon instead, but the context is clear.

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.