Skip to main content
Glama
Sign In
Nucleo for WordPress

Nucleo for WordPress

by nucleowp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

nucleo-audit-list

Read-onlyIdempotent

Lists recent ability writes with ability, outcome, and summary so you can audit changes and verify results.

Instructions

Latest writes performed by the abilities, with ability, outcome and summary.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that results are 'latest' writes and include outcome, implying recency ordering and success/failure records. It does not disclose retention window, sort order, or whether outcome values are enumerated, which would be genuinely useful context for an audit tool.

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?

A single short sentence with no filler, front-loading the resource (latest writes) before the returned fields. The only weakness is awkward grammar ('performed by the abilities') that slightly obscures meaning rather than saving space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only, single-optional-parameter list tool with no output schema, the description does mention the shape of returned records, which is helpful. It still leaves key audit-tool context unstated: how far back 'latest' reaches, ordering, and what an 'ability' is. Adequate but with clear gaps.

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 0%, so the description carries the burden for the single 'limit' parameter and never mentions it. However, 'limit' on a list tool with an explicit default of 50 and bounds of 1-200 is close to self-explanatory from the schema alone. So the description neither helps nor misleads here.

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?

The description states a specific verb and resource: listing the latest write operations for audit purposes, and it names the returned fields (ability, outcome, summary). No sibling tool appears to serve an audit-log role, so it is distinguishable from the catalog/content/doc listers. It loses a point because 'abilities' is unexplained jargon and the phrasing 'latest writes performed by the abilities' is ambiguous about who performed what.

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?

There is no when-to-use guidance, no stated preconditions, and no mention of any alternative for inspecting write history or outcomes. The only hint of intended use is the word 'audit' in the tool name, which the description itself never reinforces. An agent must infer that this is the diagnostic tool for recent mutation errors.

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