Skip to main content
Glama

Get an icon as code

get_icon
Read-only

One icon in one style and format, with what it means, which icons to use instead, what it is confused with, file URLs (SVG, PNG 16/32/48), its family and, when it has one, its animated version (motion).

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": {
      "name": "<name>"
    },
    "name": "get_icon"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesIcon name, kebab-case (from search_icons)
styleNoline-round
formatNosvg

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already mark this as a safe read (readOnlyHint true, openWorldHint false), and the description goes well beyond them by enumerating the payload: meaning, alternative icons, confusions, family, motion/animated variant, and file URLs. That return-shape disclosure is real added value given there is no output schema. It does not cover failure behavior, such as what happens for an unknown icon name or unsupported style/format combination.

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?

A single sentence with no filler, and the core fact (one icon, one style, one format) is front-loaded before the payload enumeration. The remaining clause is a dense comma-separated return-field list, which reads more like an inventory than a prioritized summary, but nothing is wasted.

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 no output schema and partial parameter coverage, the description carries the right burden by spelling out what comes back and by disambiguating the format parameter's effect on returned URLs. Enough is present for correct invocation; only the error/edge-case behavior and per-style meaning are missing.

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 33% – only name is documented – but style and format are closed enums with defaults, so their meaning is largely self-evident from the schema. The description clarifies that format governs a code/asset variant while the response still carries SVG and PNG 16/32/48 URLs, which resolves a genuine ambiguity about whether format means output code flavor or image asset. It does not explain the semantic difference among the six style values.

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?

Names a specific resource (a single icon) and its scope (one style, one format), which cleanly separates it from the plural siblings get_icons and search_icons. The verb is only implied by the title rather than stated in the description, so it falls just short of a crisp verb+resource statement.

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?

Usage is only implied: the repeated emphasis on 'one icon in one style and format' signals singular lookup, and the name parameter's schema note points back to search_icons, which suggests a search-then-fetch flow. There is no explicit when-to-use/when-not statement naming get_icons or search_icons as alternatives in the description itself.

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.