Skip to main content
Glama

Get the install command and import for an AI Canvas icon

get_icon_install
Read-onlyIdempotent

Returns the shadcn install command for one AI Canvas icon, producing an editable file with shared runtime plus exact import and JSX usage. Search icon names first.

Instructions

Return the shadcn command that installs one AI Canvas icon as an editable file (components/icons/.tsx plus the shared IconBase runtime), with the exact import and JSX to use it. Line is free with an account; Duotone, Solid and Solid duotone are Premium. Find names with search_icons first.

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_install"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe icon name from search_icons, e.g. "search" or "arrow-up-right".
styleNoIcon style. Default "line".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety profile is covered; the description adds real context beyond that by naming the exact files involved and disclosing that three of the four styles are Premium (i.e., access-gated). It does not say what happens when a Premium style is requested without entitlement, leaving the failure mode unstated.

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?

Three sentences, front-loaded with the return value, then the tier constraints, then the prerequisite. Every sentence carries information that is not in the schema or annotations; nothing is repeated or padded.

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

Completeness5/5

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

There is no output schema, so the description has to describe the return payload, and it does: the install command, the editable file and runtime it produces, and the import/JSX usage. Combined with the prerequisite pointer and the Premium/free distinction, an agent has everything needed to call it and interpret the result.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents both parameters and sets the baseline at 3. The description goes further by attaching licensing meaning to the style enum values, which the enum itself does not convey, and by pointing at search_icons as the source of valid name values.

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?

States a concrete verb and object: it returns the shadcn install command for one AI Canvas icon, plus the exact import and JSX, and names the artifacts produced (components/icons/<name>.tsx and the shared IconBase runtime). That specificity is enough for an agent to distinguish it from search_icons (discovery) without opening either schema.

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?

Gives a clear prerequisite workflow — 'Find names with `search_icons` first' — and explains the licensing boundary that governs the style choice: Line is free with an account, while Duotone, Solid and Solid duotone are Premium. It does not state exclusions or how it differs from the similarly named get_install_command sibling, so it stops short of full when/when-not guidance.

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