Skip to main content
Glama
Sign In
Nucleo for WordPress

Nucleo for WordPress

by nucleowp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

nucleo-catalog-list

Read-onlyIdempotent

Lists available Nucleo blocks with title, category and short description, so you can find the right block before fetching its full manifest with catalog-get.

Instructions

List of Nucleo blocks with title, category and short description. The full manifest, with style keys, HTML and base CSS, is read with nucleo/catalog-get {name}. Rules that no manifest holds are read with nucleo/catalog-get {topic}: documents (node format, ids, section parameters), tokens, styles (with the style groups of every block), bindings, visibility, data, theme, site-files, acknowledge, components.

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-catalog-list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the description only needs to add what is not structured. It does that by naming the three fields returned and clarifying that the heavy payload (style keys, HTML, base CSS) lives behind a different call, which sets expectations about result size. No mention of pagination or ordering, but for a metadata list that is minor.

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?

Three sentences, front-loaded with the primary purpose before the routing information. The trailing topic enumeration is dense but each item maps to a real lookup path, so it earns its space; it could be tightened into a single clause.

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?

With no output schema, the description carries the burden of describing returns, and it does so by listing the three fields. Combined with the explicit pointer to catalog-get for the full manifest, an agent has enough to call this correctly and know what it will and will not get back.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. It correctly avoids inventing filter options that the schema does not support.

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?

The first sentence gives a specific verb and resource ('List of Nucleo blocks') and enumerates the returned fields (title, category, short description), which an agent can act on. It also distinguishes itself from nucleo-catalog-get by scope, though it never explains what a 'block' is in this domain, leaving a small gap for a newcomer.

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 explicitly routes the agent: use nucleo/catalog-get {name} for a full manifest and {topic} for rules not held in any manifest, with a concrete topic list. What is missing is a stated condition for when the list itself is the right call (e.g., discovery before a get) and any exclusion such as 'do not use for editing'.

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