Skip to main content
Glama

BRAINIAC WordPress Fleet Intelligence

Normalize a WordPress site inventory

wordpress-fleet_site-inventory-normalize
Read-onlyIdempotent

Copy supplied sites, plugins, and themes into a consistent inventory. Counts come from the request only. No site is logged into. Price $0.04 USDC. POST /api/v1/wordpress-fleet/site-inventory-normalize. 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-inventory-normalize"
  }
}

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.
themesNothemes. Array.
pluginsNoplugins. Array.
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, and the description goes beyond them with the price ($0.04 USDC), the x402 payment gate ("An unpaid call returns the x402 payment terms and does not run"), and the no-login guarantee. It stops short of reconciling that with the fetchPublic parameter, which does reach out to a public catalog, and says nothing about how the normalization result is shaped.

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?

Five short sentences, purpose front-loaded, with pricing and transport details after the core definition; nothing is padded. The style is telegraphic ("Price $0.04 USDC. POST /api/v1/...") but every sentence carries information an agent needs.

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?

For an 11-parameter, deeply nested tool the description covers what it does, where counts come from, cost, and the payment failure mode, and an output schema exists to explain return values. It leaves a real gap around the four mutually-exclusive-looking input channels and the one network-touching flag (fetchPublic), which an agent must resolve 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 parameters with nested objects, so the schema already carries the parameter burden and baseline 3 applies. The description adds one useful semantic note — counts derive solely from the supplied payload — but does not explain the relationship among the text/csv/json/file input alternatives or what fetchPublic triggers.

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?

"Copy supplied sites, plugins, and themes into a consistent inventory" gives a specific verb (copy/normalize) plus the three resources, and "Counts come from the request only" scopes it as a passthrough transform rather than a live scan. It does not name any sibling (e.g. risk-analyze or plugin-conflict-detect) to sharpen the boundary, so differentiation is implicit rather than explicit.

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?

"No site is logged into" and "Counts come from the request only" imply this is for normalizing data you already hold, as opposed to tools that go out and evaluate sites. There is no explicit when-to-use / when-not-to-use statement and no named alternative, so the guidance is inferable but not 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