Skip to main content
Glama
Sign In

Omakase Icons

by com.oma-kase
OverviewDiscussionsAdmin

Get icon code

get_icon
Read-only

Get ready-to-paste code for one icon: install command, import, JSX/Vue/Svelte usage, or raw SVG. Unknown names return the closest matches instead of a guess.

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
rtlNoSet true for right-to-left layouts (Arabic, Hebrew). Directional icons such as arrows and chevrons are mirrored; others are unchanged.
nameYesIcon name from search_icons, e.g. "trash" or "chevron-left".
sizeNoRendered size in px. Default 24. Stroke weight adapts automatically (16px → 2.25, 20px → 1.8, 24px → 1.5).
cornerNoCorner shape. Default rounded.
formatNoOutput format. Default react.
variantNoVisual style. Default stroke.
strokeWidthNoOverride the stroke weight on the 24px grid. Usually leave unset.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With readOnlyHint=true already declaring the safety profile, the description's added value is the fallback behavior — unknown names return nearest matches instead of an error or fabrication — which is genuine non-obvious behavior an agent should know. It stops short of describing the response shape per format or any limits on the lookup.

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?

Two front-loaded sentences with no filler; the deliverable is stated first and the edge-case behavior second. Slight density in the format enumeration, but nothing that could be cut without losing information.

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?

A seven-parameter read-only tool with no output schema needs the description to say what comes back, and it does — code artifacts per requested format. It leaves the actual response structure (single code string vs multiple fields such as install+import+usage) unspecified, which is the remaining gap for an agent assembling a call.

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 100% and the schema already documents defaults, stroke adaptation, and rtl mirroring, so it carries most of the parameter meaning. The description adds only marginal interpretation by mapping the `format` enum to concrete artifacts (install command + import + usage snippet vs raw SVG), which is a small step beyond the bare enum 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?

Specific verb and resource ("Get ready-to-paste code for one icon") plus an enumeration of what that code contains: install command, import, JSX/Vue/Svelte usage, or raw SVG. The single-icon scope implicitly contrasts with list_icons/search_icons, but the description never names those siblings — that routing hint only appears in the schema's `name` description.

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?

Clearly frames the call as per-icon code retrieval and adds a recovery path: an unknown name yields closest matches rather than a guess, so the agent knows it can retry without a hard failure. No explicit exclusion or prerequisite (e.g., 'call search_icons first to resolve a name') is stated 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.

All Omakase Icons 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