Skip to main content
Glama
Sign In

Svg/icons MCP

by com.svgicons
OverviewDiscussionsAdmin

Get icon metadata or SVG

get_icon
Read-only

Return one icon by ID. Metadata is public; raw SVG requires a Pro API token with icons:read and mcp:use scopes.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe catalog icon ID, as shown in search results and icon page URLs.
formatNosvg is an alias for includeSvg=true; metadata (default) returns metadata only.
includeSvgNoInclude the raw body and wrapped SVG markup. Requires a Pro token with icons:read. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / format / description
      Added value: +"svg is an alias for includeSvg=true; metadata (default) returns metadata only."
    • addedInput schema / properties / id / description
      Added value: +"The catalog icon ID, as shown in search results and icon page URLs."
    • addedInput schema / properties / includeSvg / description
      Added value: +"Include the raw body and wrapped SVG markup. Requires a Pro token with icons:read. Default false."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With readOnlyHint already declared, the description adds meaningful context: metadata is public, SVG requires Pro token with specific scopes (icons:read and mcp:use). This warns the agent about potential auth failures, going beyond the annotation.

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?

Two sentences: first states core function, second adds critical access constraint. Minimal waste, well-structured.

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?

For a single-icon retrieval tool with one required parameter, the description covers the essential behavioral caveat (SVG access restriction) and the schema fully documents parameters. The absence of an output schema is mitigated by the simple return type, so completeness is high.

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?

All three parameters (id, format, includeSvg) are fully described in the schema with types, defaults, and the alias relationship. The description adds no additional parameter semantics beyond what's in the schema, so baseline 3 is appropriate.

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 uses the specific verb 'Return' with the resource 'one icon by ID,' clearly distinguishing from sibling tools like get_icon_collection and search_icons. It precisely states the tool's core function.

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 description gives clear context: use this tool when you have an icon ID and need its metadata or SVG. It notes the auth prerequisite for SVG but does not explicitly mention alternative tools for discovery, relying on the ID-based scope.

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

All Svg/icons MCP toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources