Skip to main content
Glama

Get icon SVG

get_icon
Read-only

Fetch a ready-to-use icon SVG by prefix and name (e.g. ph:house, feather:home), with optional size and color, for direct insertion into code.

Instructions

Returns a ready-to-use icon SVG, e.g. ph:house, hugeicons:home-01, feather:home, pixelarticons:home.

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
nameYesprefix:name
sizeNoHeight in px; default 1em
colorNoColor, e.g. #111827 (default currentColor)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds that the return value is a ready-to-use SVG (useful since there is no output schema), but says nothing about defaults for size/color, whether the string is raw markup or a data URI, or what happens for an unknown icon name.

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?

A single front-loaded sentence with no waste; the examples are compact and directly useful for constructing a call.

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

Completeness3/5

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

For a simple three-parameter read tool with full annotation coverage this is close to adequate, but with no output schema the description should say more about the return payload and should point at the sibling for discovering icon names.

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 description coverage is 100%, so the baseline is 3. The description's four example identifiers do add real meaning to the terse 'prefix:name' schema hint by showing valid prefixes, but size and color receive no mention beyond the schema.

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 verb ('Returns') and resource ('icon SVG'), and the inline examples make clear this is a fetch-by-identifier tool rather than a search. It doesn't explicitly contrast itself with search_icons, so the boundary between looking up and fetching an icon is left implicit.

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 examples show the required 'prefix:name' form, which tells an agent how to call it but not when. There is no statement such as 'use search_icons first if you don't know the exact name', even though a sibling search_icons exists.

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