Skip to main content
Glama
Sign In
Nucleo for WordPress

Nucleo for WordPress

by nucleowp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

nucleo-mail-log

Read-onlyIdempotent

Retrieve recent Nucleo development emails, such as one-time codes and form messages, that were logged instead of sent on local or development WordPress sites.

Instructions

Emails of Nucleo (one-time codes, form emails) written to the development mail log instead of being sent: on local sites, or on development sites with NUCLEO_DEV_MAIL true; never on staging or production. Other WordPress emails are not logged. Newest first; empty when the log is off. Entries older than 24 hours are dropped. body is cut to 5000 characters.

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-mail-log"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint, and the description adds substantial behavior beyond them: 24-hour retention (entries dropped), newest-first ordering, empty-when-off semantics, and a documented 5000-character truncation of the body. These are exactly the constraints an agent needs to interpret results correctly.

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?

Every sentence carries a distinct fact — scope, environment conditions, ordering, retention, truncation — with the essential scope statement front-loaded. No filler or restatement of the tool name despite the dense colon-and-semicolon phrasing.

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 does the work of describing the return set: ordering, emptiness, retention window, and body truncation. It stops short of naming the entry fields (recipient, subject, timestamp), which leaves an agent to discover the record shape by calling it.

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?

There is one parameter (limit) with 0% schema description coverage, and the description never mentions it — it neither explains the default of 20, the hard maximum of 20, nor what 'limit' counts. The parameter is trivial and its bounds are visible in the schema, so this is a minor but real gap rather than a disqualifying one.

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?

The description names the specific resource (Nucleo emails: one-time codes and form emails written to the development mail log rather than sent) and immediately bounds the scope by excluding other WordPress emails. An agent can tell exactly what this returns and what it does not, 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?

It states the precise conditions under which the tool has data — local sites, or development sites with NUCLEO_DEV_MAIL true — and explicitly rules out staging and production, plus warns the result is empty when logging is off. That is clear when-to-expect-results guidance, though it never names an alternative tool for reading mail in other environments.

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