Skip to main content
Glama

WP Update Radar

by xyz.utilityhouse.updates
OverviewDiscussionsAdmin

Server Details

WordPress plugin release signals from public support threads, with evidence and explicit unknowns.

Ownership verified
Status
Healthy
Uptime
100.0% over 22 days
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL

TDQS

A4.5/5.0

Scored across 2 tools

Disambiguation5/5

The two tools are perfectly distinct: one checks a single plugin release, the other checks multiple plugin updates in one call. The names and descriptions make the single-vs-batch distinction unmistakable, with no overlapping responsibilities.

Naming Consistency5/5

Both tools share the domain prefix `wp_update_radar_` and the verb `check`. The batch variant is clearly marked with `_many`, creating an obvious and predictable pattern: `wp_update_radar_check` and `wp_update_radar_check_many`.

Tool Count4/5

With only 2 tools, the count is below the typical 3-15 range, but it fits a purpose-built service with a narrow scope: one single-check tool and one batched variant. It feels minimal rather than thin because both tools earn their place.

Completeness4/5

The two tools cover the core need: checking one plugin release or a whole site's plugin list. Missing features like caching or plugin-index exploration are not core to the stated purpose. The surface is fairly complete for a focused radar service.

Available Tools

2 tools
wp_update_radar_checkA
Read-onlyIdempotent
Inspect

Reports what wordpress.org's public support forum says about one plugin release, compared with the releases before it, counted the same way on both sides. It does not answer whether an update is safe: nothing here can see your site, your theme, your premium plugins or your PHP version. state is what the evidence supports doing, signal is only what was observed: HOLD elevated public signal for this release WAIT above this plugin's own normal, or the window is still open GUARDED_ROLLOUT no elevated public signal — roll out somewhere low-stakes first NOT_ENOUGH_EVIDENCE too little was attributable to judge; a gap here, NOT a finding about the release, and not a reason to reassure anyone The legacy verdict field keeps its five strings (known-bad / wait / update-now / too-new / insufficient-data) for clients that already read it. Use it before applying a plugin update, or when someone asks whether a specific version broke anything. Not a security advisory and not a CVE lookup: it reports what other site owners are saying, which is a different question from whether a release is vulnerable. wordpress.org plugins only — premium and paid plugins have no public forum to read, and themes are out of scope. Covers the most-installed plugins; one outside that set returns an error rather than a guess.

ParametersJSON Schema
NameRequiredDescriptionDefault
pluginYeswordpress.org plugin slug, e.g. "woocommerce"
versionYesExact release to check, e.g. "8.5.1"

Output Schema

ParametersJSON Schema
NameRequiredDescription
stateYeswhat to do. Separate from `signal`, which is only what was observed.
signalYeswhat the public forum showed. NO_OBSERVATION means nothing was comparable, which is not the same as nothing being wrong.
threadsYes
verdictYes
baselineYesaverage threads per release for this plugin
coverageYeshow much of this plugin's forum could be attributed at all
unknownsYeswhat this answer does not know. Never empty.
freshnessYes
attributionYeshow many threads were tied to this release and to its baseline, by the same function
reasonCodesYesfinite reasons for the state
weakEvidenceYesthreads in this version's window that named no version
lastCheckedAtYesepoch ms this plugin's forum was last swept; 0 means never
strongEvidenceYesthreads naming this exact version
baselineReleasesYeshow many other releases the baseline was drawn from

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover read-only and idempotency, and the description goes well beyond them: it details what the tool cannot see (site, theme, premium plugins, PHP version), explains the meaning of 'state' and 'signal', describes error behavior for out-of-scope plugins, and notes the legacy 'verdict' field. This is substantial behavioral disclosure that helps an agent set expectations correctly. No contradiction with annotations.

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 description is longer than typical but well structured: it front-loads the core purpose in the first sentence, then covers limitations, state/signal semantics, legacy fields, usage, and scope in a logical order. Every sentence adds contextual value, though it could be tightened without losing information. It is not verbose for the sake of verbosity, so it earns a 4.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return-value explanation is not needed, and the description covers all other necessary context: what the tool does, what it doesn't do, how to interpret results (state/signal), the legacy field, error scenarios, scope restrictions, and usage guidance. No critical information is missing for an agent to invoke it correctly.

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 tool's parameters are already fully documented in the schema ('wordpress.org plugin slug' and 'Exact release to check'). The description doesn't add further semantic value about the parameters beyond what the schema provides; it simply uses them in context. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Reports') and resource ('what wordpress.org's public support forum says about one plugin release'), and clarifies it compares against prior releases. It also distinguishes itself from security advisories and CVE lookups, so the core purpose is unambiguous. The mention of 'one plugin release' hints at differentiation from the sibling but doesn't name it, yet the purpose is still clear.

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

Usage Guidelines4/5

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

It gives explicit when-to-use context ('before applying a plugin update, or when someone asks whether a specific version broke anything') and when-not-to-use (not for security advisories, not for premium plugins/themes). However, it never mentions the sibling wp_update_radar_check_many or says when to use that instead, so the alternatives dimension is incomplete. This is a clear context but lacks explicit sibling differentiation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

wp_update_radar_check_manyA
Read-onlyIdempotent
Inspect

Answers: which of this site's plugin updates are risky right now? Prefer this over the single check whenever there is more than one plugin to look at — a whole site's plugin list costs one call here instead of one call each. Same five verdicts as the single check (known-bad, wait, update-now, too-new, insufficient-data), per item and independent: a plugin that is not indexed reports its own error and the rest still answer. Returns a count of each verdict, so the risky ones can be found without reading every row. Up to 25 plugins per call; more than that is reported, not silently cut. insufficient-data means this service does not know, which is not the same as safe. Not a security advisory and not a CVE lookup: it reports what other site owners are saying, which is a different question from whether a release is vulnerable. wordpress.org plugins only — premium plugins have no public forum to read, and themes are out of scope.

ParametersJSON Schema
NameRequiredDescriptionDefault
pluginsYesThe plugins and the exact versions in use

Output Schema

ParametersJSON Schema
NameRequiredDescription
countsYesverdict -> count, plus `error` for items that could not be judged
resultsYes
skippedYes
examinedYeshow many were actually judged, after the per-call cap
requestedYes

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, openWorldHint, idempotentHint, destructiveHint), the description discloses meaningful runtime behavior: per-item independence with its own error, verdict counts returned, a 25-item ceiling with 'more than that is reported, not silently cut', the non-safety meaning of insufficient-data, and the non-CVE/non-advisory nature. These are substantive behaviors not inferable from annotations alone.

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 description is longer than the average MCP tool, but every sentence contributes essential guidance: use case, batching rationale, verdict semantics, per-item failure, counting, limit behavior, definition of insufficient-data, scope boundary, and CVE distinction. It is front-loaded with the core answer and then expands into necessary nuance, so it earns its length without being bloated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that an output schema exists (so return format is covered structurally), the description covers all critical call-time context: what the tool does, when to use it, how to batch plugins, behavior on bad items, verdict meanings, scope restrictions, and the distinction from CVE advisories. No information an agent needs to decide to call or format the input is missing.

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?

The input schema already fully documents the single `plugins` parameter, including item shape and examples for `plugin` and `version` (schema coverage is 100%). The description adds context like 'a whole site's plugin list' and 'exact versions in use' and explains the 25-item limit behavior, but these are more usage guidelines than parameter semantics. Since the schema carries the meaning, the baseline 3 is appropriate; the description adds limited new semantic value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Answers: which of this site's plugin updates are risky right now?' and explicitly differentiates from the sibling tool with 'Prefer this over the single check whenever there is more than one plugin.' This allows an agent to distinguish the batch variant from wp_update_radar_check without needing other context.

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

Usage Guidelines5/5

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

It says exactly when to choose this tool over the single check: 'Prefer this over the single check whenever there is more than one plugin to look at' and gives a practical cost rationale. It also scopes usage by stating wordpress.org plugins only and excludes premium plugins and themes. This is clear, actionable guidance with no ambiguity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Changedwp_update_radar_check11 fields changed
      • addedOutput schema / properties / attribution
        Added value: +{
+  "additionalProperties": false,
+  "description": "how many threads were tied to this release and to its baseline, by the same function",
+  "properties": {
+    "baseline": {
+      "additionalProperties": false,
+      "properties": {
+        "attributed": {
+          "type": "integer"
+        },
+        "explicit": {
+          "type": "integer"
+        },
+        "mean": {
+          "type": "number"
+        },
+        "releases": {
+          "type": "integer"
+        },
+        "window": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "releases",
+        "explicit",
+        "window",
+        "attributed",
+        "mean"
+      ],
+      "type": "object"
+    },
+    "current": {
+      "additionalProperties": false,
+      "properties": {
+        "attributed": {
+          "type": "integer"
+        },
+        "explicit": {
+          "type": "integer"
+        },
+        "window": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "explicit",
+        "window",
+        "attributed"
+      ],
+      "type": "object"
+    },
+    "sameFunction": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "current",
+    "baseline",
+    "sameFunction"
+  ],
+  "type": "object"
+}
      • addedOutput schema / properties / coverage
        Added value: +{
+  "additionalProperties": false,
+  "description": "how much of this plugin's forum could be attributed at all",
+  "properties": {
+    "ambiguous": {
+      "type": "integer"
+    },
+    "attributedRate": {
+      "type": "number"
+    },
+    "directMappingRate": {
+      "type": "number"
+    },
+    "explicit": {
+      "type": "integer"
+    },
+    "postTimeUnknown": {
+      "type": "integer"
+    },
+    "threadsTotal": {
+      "type": "integer"
+    },
+    "unattributed": {
+      "type": "integer"
+    },
+    "window": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "threadsTotal",
+    "explicit",
+    "window",
+    "unattributed",
+    "ambiguous",
+    "directMappingRate",
+    "attributedRate",
+    "postTimeUnknown"
+  ],
+  "type": "object"
+}
      • addedOutput schema / properties / freshness
        Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "ageHours": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "lastCheckedAt": {
+      "type": "integer"
+    },
+    "stale": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "lastCheckedAt",
+    "ageHours",
+    "stale"
+  ],
+  "type": "object"
+}
      • addedOutput schema / properties / reasonCodes
        Added value: +{
+  "description": "finite reasons for the state",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
      • addedOutput schema / properties / signal
        Added value: +{
+  "description": "what the public forum showed. NO_OBSERVATION means nothing was comparable, which is not the same as nothing being wrong.",
+  "enum": [
+    "ELEVATED_PUBLIC_SIGNAL",
+    "NO_ELEVATED_PUBLIC_SIGNAL",
+    "NO_OBSERVATION"
+  ],
+  "type": "string"
+}
      • addedOutput schema / properties / state
        Added value: +{
+  "description": "what to do. Separate from `signal`, which is only what was observed.",
+  "enum": [
+    "GUARDED_ROLLOUT",
+    "WAIT",
+    "HOLD",
+    "NOT_ENOUGH_EVIDENCE"
+  ],
+  "type": "string"
+}
      • changedOutput schema / properties / threads / items / properties / thread_time / description
        Previous value: -"epoch ms the thread was posted"New value: +"epoch ms of the timestamp identified by timeBasis"
      • addedOutput schema / properties / threads / items / properties / timeBasis
        Added value: +{
+  "description": "whether thread_time is the topic creation time or only its last activity time",
+  "enum": [
+    "TOPIC_CREATED",
+    "LAST_ACTIVITY"
+  ],
+  "type": "string"
+}
      • changedOutput schema / properties / threads / items / required
        Previous value: -[
-  "title",
-  "url",
-  "thread_time",
-  "version"
-]New value: +[
+  "title",
+  "url",
+  "thread_time",
+  "version",
+  "timeBasis"
+]
      • addedOutput schema / properties / unknowns
        Added value: +{
+  "description": "what this answer does not know. Never empty.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
      • changedOutput schema / required
        Previous value: -[
-  "verdict",
-  "lastCheckedAt",
-  "baselineReleases",
-  "strongEvidence",
-  "weakEvidence",
-  "baseline",
-  "threads"
-]New value: +[
+  "verdict",
+  "lastCheckedAt",
+  "baselineReleases",
+  "strongEvidence",
+  "weakEvidence",
+  "baseline",
+  "threads",
+  "state",
+  "signal",
+  "reasonCodes",
+  "attribution",
+  "coverage",
+  "freshness",
+  "unknowns"
+]
    • Changedwp_update_radar_check_many10 fields changed
      • addedOutput schema / properties / results / items / properties / attribution
        Added value: +{
+  "additionalProperties": false,
+  "description": "how many threads were tied to this release and to its baseline, by the same function",
+  "properties": {
+    "baseline": {
+      "additionalProperties": false,
+      "properties": {
+        "attributed": {
+          "type": "integer"
+        },
+        "explicit": {
+          "type": "integer"
+        },
+        "mean": {
+          "type": "number"
+        },
+        "releases": {
+          "type": "integer"
+        },
+        "window": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "releases",
+        "explicit",
+        "window",
+        "attributed",
+        "mean"
+      ],
+      "type": "object"
+    },
+    "current": {
+      "additionalProperties": false,
+      "properties": {
+        "attributed": {
+          "type": "integer"
+        },
+        "explicit": {
+          "type": "integer"
+        },
+        "window": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "explicit",
+        "window",
+        "attributed"
+      ],
+      "type": "object"
+    },
+    "sameFunction": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "current",
+    "baseline",
+    "sameFunction"
+  ],
+  "type": "object"
+}
      • addedOutput schema / properties / results / items / properties / coverage
        Added value: +{
+  "additionalProperties": false,
+  "description": "how much of this plugin's forum could be attributed at all",
+  "properties": {
+    "ambiguous": {
+      "type": "integer"
+    },
+    "attributedRate": {
+      "type": "number"
+    },
+    "directMappingRate": {
+      "type": "number"
+    },
+    "explicit": {
+      "type": "integer"
+    },
+    "postTimeUnknown": {
+      "type": "integer"
+    },
+    "threadsTotal": {
+      "type": "integer"
+    },
+    "unattributed": {
+      "type": "integer"
+    },
+    "window": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "threadsTotal",
+    "explicit",
+    "window",
+    "unattributed",
+    "ambiguous",
+    "directMappingRate",
+    "attributedRate",
+    "postTimeUnknown"
+  ],
+  "type": "object"
+}
      • addedOutput schema / properties / results / items / properties / freshness
        Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "ageHours": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "lastCheckedAt": {
+      "type": "integer"
+    },
+    "stale": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "lastCheckedAt",
+    "ageHours",
+    "stale"
+  ],
+  "type": "object"
+}
      • addedOutput schema / properties / results / items / properties / reasonCodes
        Added value: +{
+  "description": "finite reasons for the state",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
      • addedOutput schema / properties / results / items / properties / signal
        Added value: +{
+  "description": "what the public forum showed. NO_OBSERVATION means nothing was comparable, which is not the same as nothing being wrong.",
+  "enum": [
+    "ELEVATED_PUBLIC_SIGNAL",
+    "NO_ELEVATED_PUBLIC_SIGNAL",
+    "NO_OBSERVATION"
+  ],
+  "type": "string"
+}
      • addedOutput schema / properties / results / items / properties / state
        Added value: +{
+  "description": "what to do. Separate from `signal`, which is only what was observed.",
+  "enum": [
+    "GUARDED_ROLLOUT",
+    "WAIT",
+    "HOLD",
+    "NOT_ENOUGH_EVIDENCE"
+  ],
+  "type": "string"
+}
      • changedOutput schema / properties / results / items / properties / threads / items / properties / thread_time / description
        Previous value: -"epoch ms the thread was posted"New value: +"epoch ms of the timestamp identified by timeBasis"
      • addedOutput schema / properties / results / items / properties / threads / items / properties / timeBasis
        Added value: +{
+  "description": "whether thread_time is the topic creation time or only its last activity time",
+  "enum": [
+    "TOPIC_CREATED",
+    "LAST_ACTIVITY"
+  ],
+  "type": "string"
+}
      • changedOutput schema / properties / results / items / properties / threads / items / required
        Previous value: -[
-  "title",
-  "url",
-  "thread_time",
-  "version"
-]New value: +[
+  "title",
+  "url",
+  "thread_time",
+  "version",
+  "timeBasis"
+]
      • addedOutput schema / properties / results / items / properties / unknowns
        Added value: +{
+  "description": "what this answer does not know. Never empty.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. 2 tool updates
    • First observedwp_update_radar_check
    • First observedwp_update_radar_check_many

Related MCP Connectors

Related MCP Servers

  • wpgoldmine-mcp

    Bishop81
    A
    license
    A
    quality
    D
    maintenance
    Enables AI agents to discover WordPress plugin opportunities by querying the WordPress.org directory for abandoned, low-rated, or unsupported plugins that can be replaced or out-built.
    3
    33 npm
    MIT

  • WordPress Meta Trac MCP Server

    courtneyr-dev
    F
    license
    Not graded
    quality
    D
    maintenance
    Provides AI assistants with comprehensive access to WordPress Meta Trac data, enabling intelligent queries about WordPress.org infrastructure, plugin/theme directories, WordCamp events, and other WordPress.org services through ticket searches, changeset information, and activity monitoring.
    2
    -

  • Releases MCP Server

    buildinternet
    A
    license
    Not graded
    quality
    A
    maintenance
    A registry of product release notes from across the web, normalized, summarized, and queryable via MCP. Enables agents and developers to search and retrieve the latest releases from hundreds of vendors.
    89 npm
    7
    Apache 2.0
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources