pom_cache_get_status: inspect cache status
Reports whether POM Cache is installed, which caches it supports, and their current statistics.
Arguments
None.
Permissions
mcp:read, plus manage_options. Note that this is administrator-level for a read — most read tools in POM AI need much less.
What it returns
| Field | Meaning |
|---|---|
available |
Whether POM Cache is installed and its clearing function is loaded |
html_cache_supported |
Whether the HTML cache can be cleared |
json_cache_supported |
Whether the progressive JSON cache can be cleared |
html_stats |
The HTML cache's stored statistics |
json_stats |
The JSON cache's stored statistics |
available and html_cache_supported are the same check
Both report whether POM Cache's site-clearing function exists. They will never disagree.
json_cache_supported is a genuinely separate check: a site can have the HTML cache and not the progressive JSON one, typically because it runs an older POM Cache or does not use progressive loading.
That distinction is what pom_cache_clear_site_cache uses to decide whether the JSON purge is even attempted.
The tool exists even when POM Cache does not
Both cache tools are registered unconditionally, unlike the POM Theme tools which vanish when their plugin is absent.
So finding pom_cache_get_status in a client's tool list tells you nothing about whether POM Cache is installed. available is the answer, and it is the reason to call this before the clear tool:
Check the POM Cache status and tell me whether clearing the cache is possible here.
An available of false means pom_cache_clear_site_cache will return pom_ai_mcp_pom_cache_unavailable.
The statistics reset when you clear
Both stats options are deleted as part of a purge. So the numbers you read here describe the cache since the last clear, not since the site was built.
Two consequences:
- Reading the stats immediately after a purge returns empty ones. That is expected, not a fault.
- Comparing stats across a purge is meaningless. If you want a before-and-after picture, read them, clear, then let the cache warm up before reading again.
An empty stats set is normal
You get an empty structure when the cache has just been cleared, when the site is newly built, or when POM Cache is not installed at all.
Check available before interpreting empty statistics as a problem. On a site without POM Cache, empty is simply the truth.
What the statistics are for
They describe how much cached output exists. That is useful for two questions:
- Is the cache doing anything? A site with substantial cached output is one where a purge will have a noticeable effect on the next few page loads.
- Was the purge effective? Empty stats after a clear confirm the options were reset; combined with
html_deletedfrom the clear tool, that is reasonable evidence the files went.
What they cannot tell you is whether a specific page is cached. There is no per-URL inspection, and no way to purge one page. See Limited cache access.
It covers this site only
On a multisite network, the statistics are for the site you are connected to. Other sites in the network have their own POM Cache state, reachable only from their own connections.
It reads nothing sensitive
Availability flags and aggregate counters. No page contents, no URLs, no visitor data. Safe to include in diagnostics.
Using it well
Before a purge:
Check the cache status, then clear the cache if it is available.
Diagnosing a stale site:
Is POM Cache active here, and does it support the JSON cache?
Common problems
| Symptom | Cause |
|---|---|
pom_ai_mcp_forbidden |
Missing manage_options |
available is false |
POM Cache is not installed or not loaded |
json_cache_supported is false |
This POM Cache does not expose a JSON purge |
| Empty statistics | Just cleared, newly built, or POM Cache absent |
| Statistics look lower than expected | They reset on every purge |
| No per-page information | Not available; the cache is all-or-nothing here |