Skip to main content
Glama

BRAINIAC WordPress Fleet Intelligence

Audit WordPress plugin versions

wordpress-fleet_plugin-version-audit
Read-onlyIdempotent

Compare installed plugin versions with caller-supplied or WordPress.org public releases. An older version is a version-age warning. A vulnerability is listed only when the caller supplied it. Price $0.05 USDC. POST /api/v1/wordpress-fleet/plugin-version-audit. An unpaid call returns the x402 payment terms and does not run.

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": "wordpress-fleet_plugin-version-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNocsv, string, length 0 to 200000. Optional.
fileNofile, object. Optional.
jsonNojson, string, length 0 to 200000. Optional.
textNotext, string, length 0 to 200000. Optional.
sitesNosites, array. Optional.
themesNothemes, array. Optional.
pluginsNoplugins, array. Optional.
conflictsNoconflicts, array. Optional.
fetchPublicNofetchPublic, boolean. Optional.
publicCatalogNopublicCatalog, array. Optional.
vulnerabilitiesNovulnerabilities, array. Optional.

Output Schema

NameRequiredDescriptionDefault
itemsNoitems. Array.
statusNostatus. String.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
updateSafeNoupdateSafe. Boolean.
limitationsNolimitations. Array.
requestsSentNorequestsSent. Number.
siteAccessedNositeAccessed. Boolean.
updateInstalledNoupdateInstalled. Boolean.
websiteModifiedNowebsiteModified. Boolean.
vulnerabilityInventedNovulnerabilityInvented. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld). The description adds genuinely non-obvious behavior: the $0.05 USDC price, the x402 payment gate where an unpaid call returns payment terms and 'does not run', and the output rule that old versions produce version-age warnings. The main gap is that it doesn't say what happens when fetchPublic is off and no publicCatalog is supplied.

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?

Front-loaded with purpose, then the two output rules, then cost, endpoint, and the payment caveat. Four short sentences with no filler; the payment caveat at the end is slightly buried but each sentence earns its place.

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 an output schema present and rich annotations, the description doesn't need to explain return values, and it covers scope, pricing, and payment gating. Remaining gaps are minor: default behavior of fetchPublic and whether sites/plugins are both required for a meaningful audit.

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 11 parameters are documented in the schema; baseline is 3. The phrase 'caller-supplied or WordPress.org public releases' hints at the fetchPublic/publicCatalog mechanism but adds no format or default detail beyond the schema for the nested sites/plugins/themes/vulnerabilities structures.

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: 'Compare installed plugin versions with caller-supplied or WordPress.org public releases.' The plugin focus implicitly distinguishes it from the theme-version-audit sibling, but it never names that sibling or explicitly draws the boundary.

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?

Implied usage is clear (auditing installed plugin versions against a catalog), and 'A vulnerability is listed only when the caller supplied it' usefully tells the agent it must provide vulnerability data itself. However, there is no explicit when-to-use vs. alternative guidance, and no mention of siblings like update-compatibility-check or risk-analyze.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources