Skip to main content
Glama
Sign In
Nucleo for WordPress

Nucleo for WordPress

by nucleowp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

nucleo-model-validate

Read-onlyIdempotent

Validate a content model before saving and get its errors plus differences from the saved version. Nothing is written, so you can check post types, taxonomies, and field groups safely.

Instructions

Checks a content model without saving it, with the same rules as model-set (postTypes, taxonomies or fieldGroups not sent keep their saved value). Returns the errors and the differences from the saved model. Nothing is written. Format: catalog-get {topic: model}.

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": {
      "model": "<model>"
    },
    "name": "nucleo-model-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesContent model document.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only and idempotent, but the description adds real behavior beyond them: the merge semantics (unspecified postTypes/taxonomies/fieldGroups retain saved values) and the return contents (errors plus diff against the saved model). The pointer to 'catalog-get {topic: model}' for the document format is useful but cryptically worded.

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 short sentences, front-loaded with the core behavior and safety guarantee. The trailing 'Format: catalog-get {topic: model}' is terse to the point of ambiguity but does convey a disambiguating pointer with no filler.

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 a read-only tool with a nested model object, no output schema, and high schema coverage, the description covers safety, partial-input behavior, and return contents. The one gap is that the structure of the nested model document is only referenced indirectly via catalog-get rather than described.

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 the single 'model' parameter is already documented, so the baseline is 3. The description earns an extra point by explaining partial-model semantics — omitted sections keep their persisted values — which materially changes how the agent should construct the payload.

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?

States a specific verb and resource ('Checks a content model without saving it') and immediately anchors it against the sibling nucleo-model-set by saying it applies the same rules but writes nothing. An agent can tell validate apart from set without opening either schema.

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?

The 'without saving it' and 'Nothing is written' phrasing makes the use case (validate before applying) clear, and naming model-set as the rule-equivalent gives the natural next step. It stops short of an explicit 'use this before model-set' instruction or any exclusion, so not quite a 5.

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