Skip to main content
Glama

BRAINIAC WordPress Fleet Intelligence

Report a WordPress agency fleet

wordpress-fleet_agency-report
Read-onlyIdempotent

Combine the inventory, version audits, compatibility metadata, conflict flags, and maintenance priorities. The report does not log into sites or install updates. Price $0.12 USDC. POST /api/v1/wordpress-fleet/agency-report. 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_agency-report"
  }
}

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
levelNolevel. String.
sitesNosites. Array.
statusNostatus. String.
themesNothemes. Array.
pluginsNoplugins. Array.
signalsNosignals. Array.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
conflictsNoconflicts. Array.
siteCountNositeCount. Number.
prioritiesNopriorities. Array.
themeCountNothemeCount. Number.
updateSafeNoupdateSafe. Boolean.
limitationsNolimitations. Array.
pluginCountNopluginCount. Number.
requestsSentNorequestsSent. Number.
siteAccessedNositeAccessed. Boolean.
compatibilityNocompatibility. Array.
conflictCountNoconflictCount. Number.
outdatedCountNooutdatedCount. Number.
updateInstalledNoupdateInstalled. Boolean.
websiteModifiedNowebsiteModified. Boolean.
highPrioritySitesNohighPrioritySites. Number.
vulnerabilityInventedNovulnerabilityInvented. Boolean.
knownVulnerabilityCountNoknownVulnerabilityCount. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, it discloses the paid x402 flow, the $0.12 USDC cost, the transport (POST /api/v1/wordpress-fleet/agency-report), and critically that an unpaid call returns payment terms without executing. That failure mode is exactly the kind of behavior an agent cannot get from structured fields.

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?

Sentences are short and the aggregation scope is front-loaded. The middle sentences pack price, endpoint, and payment failure mode together, which is slightly dense but still readable and free of filler.

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 optional parameters, deep nesting, and multiple ingestion channels (sites arrays, csv, text, json, file, fetchPublic), the description omits how those input modes relate and whether data must be supplied or can be fetched. The output schema covers return values, so that gap is acceptable, but the input-mode ambiguity is not.

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 the nested sites/plugins/themes/conflicts shapes are already documented in structured data. The description adds no parameter-level meaning, such as which input mode to use (sites payload vs. csv/file/json vs. fetchPublic), so the baseline of 3 applies.

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 uses a specific verb ("Combine") and enumerates the exact artifacts aggregated: inventory, version audits, compatibility metadata, conflict flags, maintenance priorities. That makes it distinguishable from the individual sibling auditors, though it never names them explicitly.

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 implied rather than stated: an agent can infer this is the consolidated roll-up of the per-domain sibling tools. The only explicit boundary is a negative one ("does not log into sites or install updates"), with no positive guidance on when to prefer this over calling the individual analyses.

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