Skip to main content
Glama
Design Atlas MCP

Design Atlas MCP

by Tradelord223

get_icon

Read-onlyIdempotent

Retrieve an icon's complete inline SVG, upstream version, license text, and accessible usage by pack and name so coding agents can reuse it with proper attribution and accessibility.

Instructions

Get the complete inline SVG, its upstream version, license text and accessible usage.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
packYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is fully covered. The description adds genuine value by enumerating the returned payload (SVG, version, license, accessibility notes), which matters because there is no output schema. It stops short of stating behavior on missing icons or pack/name lookup failures.

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 zero filler; every clause names a distinct returned artifact. Nothing is repeated from the structured fields.

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?

The return payload is well covered, which is important given no output schema exists. However, for a two-required-parameter lookup tool with no parameter documentation anywhere, the definition leaves the caller guessing how to construct a valid pack/name pair.

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% for two required parameters (pack, name), and the description says nothing about them — no format, no relationship to pack identifiers, no case-sensitivity or slug rules. With the schema providing only type and length constraints, the description should compensate but does not.

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?

States a specific verb ("Get") and a specific payload (inline SVG, upstream version, license text, accessible usage), so an agent knows exactly what comes back. It does not differentiate itself from sibling tools like search_icons or list_icon_packs, which is the only thing keeping it from a 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no mention of alternatives such as search_icons for discovery versus this tool for retrieval. The agent must infer the usage from the name alone.

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