Skip to main content
Glama

BRAINIAC WordPress Fleet Intelligence

Check update compatibility metadata

wordpress-fleet_update-compatibility-check
Read-onlyIdempotent

Compare a site's stated WordPress and PHP versions with public requires and tested fields. A match is not treated as proof that an update is safe. Price $0.05 USDC. POST /api/v1/wordpress-fleet/update-compatibility-check. 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_update-compatibility-check"
  }
}

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.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the bar is lower, and the description still adds real behavioral context: a $0.05 USDC price, an x402 payment gate, and the fact that an unpaid call returns payment terms and does not execute. What it omits is whether it fetches public metadata itself (the fetchPublic flag) or requires the caller to supply it.

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?

The purpose is front-loaded in the first sentence, followed by a caveat and compact operational notes on price, endpoint, and payment behavior. Every sentence earns its place, though the raw endpoint path is somewhat low-value for an agent.

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?

With 11 all-optional, deeply nested parameters and a rich output schema, the description should clarify at minimum what input combination is required (sites vs. publicCatalog vs. fetchPublic). It explains cost and execution behavior but leaves the caller to infer the viable input shape from the schema alone.

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% across 11 optional parameters, so the schema already carries the per-field documentation. The description's mention of 'stated WordPress and PHP versions' and 'public requires and tested fields' loosely maps to sites[] and publicCatalog[] but adds no format or selection detail beyond that.

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 gives a concrete verb and resource: 'Compare a site's stated WordPress and PHP versions with public requires and tested fields.' That is specific enough to distinguish it from the audit/risk siblings. It stops short of naming which sibling handles the adjacent job, so it lands at 4 rather than 5.

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 by the purpose statement; there is no explicit 'use this when...' or 'use plugin-version-audit instead for...'. The caveat that a match 'is not treated as proof that an update is safe' helps an agent interpret results but is not selection guidance.

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