Skip to main content
Glama

BRAINIAC WordPress Fleet Intelligence

Detect possible plugin conflicts

wordpress-fleet_plugin-conflict-detect
Read-onlyIdempotent

Flag duplicate active plugin slugs and caller-supplied conflict pairs. A match is not a confirmed runtime conflict. Price $0.04 USDC. POST /api/v1/wordpress-fleet/plugin-conflict-detect. 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_plugin-conflict-detect"
  }
}

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

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

Beyond the annotations (readOnly, idempotent, non-destructive, open-world), it discloses the cost ($0.04 USDC), the transport (POST endpoint), and the payment-failure behavior (an unpaid call returns x402 terms and does not run). The caveat that a match is not a confirmed runtime conflict is useful output-semantics context. It omits rate limits or whether the caller must always supply one of the free-form input formats.

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 behavior and followed by the caveat, price, endpoint, and payment behavior. Every sentence carries distinct information with no 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?

The output schema and annotations carry much of the load, and the description covers the core logic plus billing. However, for an 11-parameter tool with nested objects and multiple alternative input formats (text/csv/json/file), the description gives no hint about which input channel to use or what the tool requires to be useful.

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 the baseline is 3. The description does add some meaning by highlighting that only *active* plugin slugs count and that conflict pairs are caller-supplied, which clarifies the `plugins.active` and `conflicts.left/right` fields. It says nothing about the eleven alternative input channels (text/csv/json/file) or `fetchPublic`.

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?

Uses a specific verb and resource: "Flag duplicate active plugin slugs and caller-supplied conflict pairs." It also adds an important interpretation boundary, "A match is not a confirmed runtime conflict." It does not name a sibling tool to distinguish itself from, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what gets flagged but gives no when-to-use guidance, no prerequisites, and no comparison to related tools such as update-compatibility-check or risk-analyze. The only guidance offered is interpretive (a match is not a confirmed conflict), not situational.

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