Skip to main content
Glama

BRAINIAC WordPress Fleet Intelligence

Prioritize site maintenance

wordpress-fleet_site-maintenance-priority
Read-onlyIdempotent

Rank supplied sites by outdated software, caller-supplied vulnerability matches, compatibility gaps, and conflict flags. The ranking does not approve an update. Price $0.04 USDC. POST /api/v1/wordpress-fleet/site-maintenance-priority. 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_site-maintenance-priority"
  }
}

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

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, and the description adds genuinely new behavior: the $0.04 USDC price, the x402 payment flow, and the fact that an unpaid call returns payment terms and does not execute. It also clarifies the output is a ranking, not an approval. Missing details are minor — no note on ranking determinism or tie-breaking.

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?

Five short sentences, front-loaded with the purpose, then the key caveat, then price, endpoint, and payment failure mode. Every sentence carries information an agent needs; nothing is restated from the schema or annotations.

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?

For an 11-parameter, nested-input tool with an output schema, the description covers purpose, advisory-only semantics, payment requirements, and the unpaid-call behavior, which are the non-obvious pieces. The remaining gaps — how the four body-encoding alternatives (csv/json/text/file) are chosen and how sites join to plugins/themes — are left to the schema, which documents them.

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 schema already documents all 11 parameters and the nested item shapes. The description adds only light mapping — vulnerability matches are caller-supplied, and conflicts feed the ranking — but does not explain how sites/plugins/themes correlate via siteId or how the csv/file/json/text body alternatives interact. Baseline 3 is appropriate when the schema carries the load.

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 opens with a specific verb and scope: "Rank supplied sites by outdated software, caller-supplied vulnerability matches, compatibility gaps, and conflict flags." That tells an agent exactly what the tool computes and on what inputs. It stops short of naming a sibling (e.g. risk-analyze or update-compatibility-check) as the alternative, so the boundary with adjacent tools is left implicit.

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?

There is one useful scope exclusion — "The ranking does not approve an update" — which tells the agent this is advisory, not an update trigger. However, there is no positive when-to-use statement and no routing against the closely related siblings such as wordpress-fleet_risk-analyze or wordpress-fleet_update-compatibility-check. Usage is implied by the ranking criteria rather than stated.

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