Skip to main content
Glama
Sign In

Designers

by com.allthepossibles
OverviewDiscussionsAdmin

Icon set audit

audit_icon_set
Read-only

Audits a set of inline SVG icons. Pass icons as markup containing one (or ) per icon. Reports mixed viewBox sizes, missing viewBox, non-square boxes, width and height ratios that disagree with the viewBox, mixed outline and solid styles, stroke widths and linecap or linejoin that vary, hard-coded colors instead of currentColor, icons neither aria-hidden nor named (WCAG 1.1.1), icons with both, ids repeated across icons, path points outside the viewBox, and icons that fill the artboard very differently from the median. Path extents use command endpoints only and only data. Stroke and grid expectations are conventions. Static; nothing is rendered.

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": {
      "icons": "<icons>"
    },
    "name": "audit_icon_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconsYesMarkup with several <svg> elements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Goes beyond annotations by stating the tool is static and nothing is rendered, and by disclosing important analysis limitations: path extents use command endpoints only and only <path> data, and stroke/grid expectations are conventions. These details help an agent understand the tool's behavioral boundaries.

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?

The description is front-loaded with purpose and input guidance, then lists relevant checks. It is dense but every clause identifies a concrete audit check; it could be more scannable with bullets, but there is little wasted text.

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?

For a single-parameter, read-only audit tool with no output schema, the description is complete enough: it explains input format, enumerates the report contents, and notes analytical limitations. An agent can invoke it correctly without further context.

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?

With only one parameter and full schema description coverage, the schema already defines the input. The description adds useful semantics by clarifying that each icon is one <svg> or <symbol> and that markup may contain multiple icons, which is more precise than the schema's generic wording.

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 and resource: "Audits a set of inline SVG icons." It clearly explains the scope and lists the checks performed, so an agent can understand the tool's function. However, it does not explicitly distinguish itself from the sibling check_svg_bloat, which may overlap.

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?

Provides clear input guidance: pass icons as markup containing one <svg> or <symbol> per icon. It does not state when to use this tool versus alternatives like check_svg_bloat or plan_asset_exports, nor does it specify when not to use it.

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

All Designers 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