Skip to main content
Glama

BRAINIAC WordPress Fleet Intelligence

Audit WordPress theme versions

wordpress-fleet_theme-version-audit
Read-onlyIdempotent

Compare installed theme versions with caller-supplied or WordPress.org public releases. An older version is a version-age warning, not a confirmed vulnerability. Price $0.05 USDC. POST /api/v1/wordpress-fleet/theme-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_theme-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 declare readOnly, idempotent, non-destructive, open-world behavior, and the description adds material context beyond them: a $0.05 USDC price, the POST endpoint, and the critical fact that an unpaid call returns x402 payment terms without executing. That payment-gating behavior is not derivable from the annotations. It stops short of describing rate limits or result coverage, which the output schema partially handles.

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?

Four short sentences, front-loaded with the core purpose and followed by the caveat, then the commercial and transport facts. Every sentence carries distinct information with no redundancy.

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?

The tool is complex: 11 parameters including nested arrays and four alternative payload channels (csv, file, json, text). The description never explains which input channel to use or how they relate, leaving a real gap despite the output schema and rich annotations covering returns and safety. Payment and endpoint details are well covered.

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 coverage is 100%, so all 11 parameters, including nested sites/themes/plugins/conflicts/vulnerabilities objects, are documented in the schema itself. The description only gestures at 'caller-supplied' data and adds no syntax or format detail beyond that. Baseline 3 applies when the schema carries the parameter burden.

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: comparing installed theme versions against caller-supplied or WordPress.org public releases. It also draws a clear semantic line between a version-age warning and a confirmed vulnerability. It does not name the sibling plugin-version-audit counterpart, so an agent must infer the split between theme and plugin auditing.

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: it says what gets compared and where the comparison data comes from, which suggests when the tool is appropriate, but offers no explicit when-to-use or when-not-to-use guidance versus the sibling audit tools. The 'older version is a warning, not a confirmed vulnerability' sentence guides interpretation of results rather than tool selection.

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