Skip to main content
Glama
Sign In
Nucleo for WordPress

Nucleo for WordPress

by nucleowp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

nucleo-doc-list

Read-onlyIdempotent

List Nucleo documents with IDs, titles, statuses, revisions, links, and quality-check results; filter by post type, search text, status, quality, or page.

Instructions

List of Nucleo documents with id, title, status, revision, link and quality (last check). Filters: post type, text search, status, quality, page.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
searchNo
statusNoPost status, or a list of them. Default: all except trash.
qualityNoerrors: with errors; warnings: with warnings and no errors; clean: checked with no issues.
postTypeNoPost type, e.g. "page". Default: all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds one useful behavioral detail — that 'quality' reflects the last check rather than a live audit — but says nothing about result limits, default page size, or ordering, which matter for a paginated list.

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?

A single compact sentence that front-loads the resource and return fields, then the filters. No filler or redundancy.

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, listing the returned fields in the description is the right compensating move, and it is done well. The remaining gap is pagination behavior (default page size, total counts, ordering), which an agent would need to page correctly.

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 60%: status, quality and postType carry their own schema descriptions, while search and page do not. The description compensates by naming all five filters (post type, text search, status, quality, page), mapping each to a parameter, though it adds no format or default details beyond the names.

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 ('List of Nucleo documents') and enumerates the returned fields (id, title, status, revision, link, quality), so an agent knows exactly what it retrieves. It does not distinguish itself from the sibling nucleo-docs-search, even though its 'text search' filter overlaps with that tool's apparent role, so it falls short of a 5.

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

Usage Guidelines2/5

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

The description only says 'Filters: ...' with no statement of when to use this listing tool versus nucleo-docs-search or the get/patch siblings, and no prerequisites or exclusions. Usage is implied by the filter enumeration but never stated.

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