freeicon-mcp

lg_validate

Validates brand-grade logo SVGs: filters security risks, checks offline self-containment, fallback fonts, stroke legibility, and viewBox aspect, returning normalized SVG with warnings to iterate.

Instructions

Validate a logo SVG (brand-grade, stricter than g_validate): security filter, self-contained check (rejects /external refs — logos must work offline), text fallback-font check, stroke legibility for small sizes, semantic group suggestions, viewBox/aspect sanity. Returns the normalized SVG with warnings to iterate on.

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": {
      "svg": "<svg>"
    },
    "name": "lg_validate"
  }
}

Input Schema

Name	Required	Description	Default
`svg`	Yes	The logo SVG markup to validate (root element must be <svg>)
`format`	No	Declared format — icon expects a square viewBox, wordmark/combination a 2:1 horizontal	icon

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.4Nov 9, 2026

TDQS

A4.5/5.0

Behavior5/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it does so thoroughly: security filtering, offline self-containment, rejection of <image>/external refs, text fallback checks, stroke legibility, group suggestions, and viewBox sanity are all disclosed. It also states the return behavior as a normalized SVG with warnings for iteration.

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?

The description is front-loaded with the core purpose and sibling differentiation, then efficiently lists the specific checks, then states the return shape. Every clause adds useful validation context without filler.

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, but the description explains the return value as a normalized SVG with warnings to iterate on. For a two-parameter validator, the listed checks and self-containment rule give an agent enough to invoke it and interpret the outcome.

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%: both the svg and format parameters are documented in the schema, including format enum semantics. The description adds little parameter-level detail beyond mentioning viewBox/aspect sanity, so the schema does the heavy lifting and the 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 states a specific verb and resource: validate a logo SVG. It immediately distinguishes this from the sibling g_validate by calling it brand-grade and stricter, so an agent can route correctly.

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?

It names g_validate as a less strict alternative and frames this tool as the brand-grade logo validator, giving clear context for selection. It stops short of explicit when-not guidance or saying when to prefer g_validate over this tool for generic SVGs.

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