Skip to main content
Glama
Sign In
Nucleo for WordPress

Nucleo for WordPress

by nucleowp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

nucleo-doc-preview

Read-onlyIdempotent

Compile a saved or unsaved document to preview HTML and CSS without saving, and use a context post to fill dynamic slots so you can see product layouts on a real product.

Instructions

Compiles a document without saving it and returns HTML and CSS. Accepts document or postId. With contextPostId the dynamic slots (woo/*, bindings) are filled as on the page of that post: use it to see a product layout on a real product.

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-preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
postIdNoSaved document to compile.
documentNoNucleo document to compile.
contextPostIdNoPost whose page fills the dynamic slots, for example a product id from content-list with type "product". Without it the slots stay empty.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds real value beyond that by stating nothing is persisted and that dynamic slots (woo/*, bindings) stay empty unless contextPostId is supplied. It does not, however, cover cost/size of the returned HTML/CSS or error behavior for an invalid document.

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?

Three short sentences with the outcome front-loaded, then the input alternatives, then the contextPostId semantics. No filler and nothing repeated from the schema verbatim.

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 correctly carries the return-value burden (HTML and CSS). For a compile-only tool with full schema coverage this is nearly complete; only error/failure behavior and the shape of the returned CSS/HTML payload are unaddressed.

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 description coverage is 100%, so the baseline is 3. The description does add the important either/or relationship ("Accepts document or postId") that the schema leaves implicit since both params are optional, and clarifies the slot-filling effect of contextPostId.

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 ("Compiles a document") plus the deliverable ("returns HTML and CSS"), and the qualifier "without saving it" separates it from the create/publish siblings in the same namespace. An agent can tell what this does and what it does not do without opening the 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?

Gives a concrete scenario for the main variant: "use it to see a product layout on a real product" with contextPostId set. It does not name alternatives or say when to prefer nucleo-doc-get or nucleo-doc-create instead (e.g. to persist a compiled result), so the guidance is clear but not exclusionary.

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