Skip to main content
Glama
Sign In
Nucleo for WordPress

Nucleo for WordPress

by nucleowp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

nucleo-doc-patch

Applies ordered patch operations to an existing WordPress document, enforcing base revision matching to prevent conflicts; use dryRun to preview changes without saving.

Instructions

Applies patch operations to an existing document. baseRevision must match the current revision, otherwise it returns conflict. With dryRun true it does not save.

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": {
      "postId": "<postId>",
      "baseRevision": "<baseRevision>",
      "ops": "<ops>"
    },
    "name": "nucleo-doc-patch"
  }
}

Input Schema

NameRequiredDescriptionDefault
opsYesOperations applied in order.
dryRunNo
postIdYes
publishNo
acknowledgeNoAcknowledged quality issues, with a reason.
baseRevisionYesRevision read before the change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false), the description discloses optimistic concurrency behavior (baseRevision mismatch returns conflict) and that dryRun suppresses persistence. It does not say whether the operation is atomic, what happens to partially applied ops, or how the publish/acknowledge flags change behavior.

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, front-loaded with the action, then the conflict precondition, then the dry-run caveat. No filler or restatement of the name.

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 six-parameter mutation tool with no output schema, it covers the two behaviors an agent most needs to call it safely: the revision precondition and a safe trial mode. Gaps remain around the publish and acknowledge parameters and around atomicity/error behavior beyond the conflict case.

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?

At 50% schema coverage, the description adds real meaning for two parameters (baseRevision as the revision read before the change, dryRun as a non-persisting preview). It says nothing about ops ordering semantics beyond the schema's own note, nor about publish, acknowledge, or postId, so half the parameters remain explained only by terse schema text.

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: 'Applies patch operations to an existing document.' This clearly separates it from creation (nucleo-doc-create) and from reads, but it never explicitly contrasts itself with other mutation siblings such as nucleo-doc-rollback or nucleo-doc-texts-set.

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

Usage Guidelines3/5

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

Usage is only implied: the tool is for modifying an existing document, and the baseRevision rule tells the agent a prior read is required. There is no explicit when-to-use/when-not guidance and no named alternative for cases like restoring a prior state or setting a single text field.

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