Skip to main content
Glama
Sign In
Nucleo for WordPress

Nucleo for WordPress

by nucleowp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

nucleo-icons-set

Idempotent

Add, replace, or remove site icons for nc/icon while keeping other icons unchanged. Use it to update built-in icons globally across nc/menu and nc/list.

Instructions

Adds, replaces or removes site icons for nc/icon and leaves the others as they are. set: name (a-z, 0-9, -) → SVG markup; remove: names. A site icon with the name of a built-in icon (phone, close, chevron-down...) replaces it everywhere, also inside nc/menu and nc/list. Colors become currentColor; scripts, styles, links and unknown elements are removed. At most 300 icons. To import a folder of SVG files or icons of a library (mdi:car, lucide:truck) use the CLI: nucleo icons import , nucleo icons add prefix:name.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nucleo-icons-set"
  }
}

Input Schema

NameRequiredDescriptionDefault
setNoIcons to add or replace: name → SVG markup.
removeNoNames of site icons to remove.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, but the description adds substantial behavior beyond them: normalization to currentColor, stripping of scripts/styles/links/unknown elements, the 300-icon cap, and cross-cutting replacement for built-in names. These side-effect details are exactly what an agent needs before invoking a mutation tool.

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?

It is front-loaded and dense: scope, input mapping, collision behavior, sanitization, limits, then the CLI exit ramp. Every sentence carries distinct information, though the built-in icon parentheticals and CLI command strings make it slightly crowded.

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?

For two nested-object parameters, no output schema, and idempotent/destructive annotations, the description covers mutation semantics, sanitization, limits, and alternatives well. It stops short of describing the return shape or whether a partially failed bulk set rolls back, which would matter for a bulk mutation.

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% and already documents set as name→SVG markup and remove as names of site icons. The description adds meaning: the name character constraint (a-z, 0-9, -) and the precedence behavior when a name collides with a built-in icon. Since the nested additionalProperties type is covered by the schema, 4 is appropriate rather than 5.

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 set (adds, replaces, removes) and resource (site icons for nc/icon) and sharply scopes it: it touches only the named icons and leaves the others as they are. This differentiates it from broad settings mutators in the sibling list.

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

Usage Guidelines5/5

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

It explicitly names the case where this tool is wrong and the alternative: importing an SVG folder or library icons (mdi:car, lucide:truck) should use the CLI with named commands. It also flags the collision case where a built-in icon name (phone, close, chevron-down) replaces everywhere, including nc/menu and nc/list.

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

Deploy Server

Other Tools