pom_theme_get_status: inspect POM Theme status
Reports whether POM Theme is usable on this site, and what the active theme actually is.
Arguments
None.
Permissions
mcp:read and pom_theme:read, plus edit_theme_options.
It is the one tool that is always registered
Every other tool in this chapter and the template chapter is registered only when POM Theme is available. This one is registered unconditionally.
That makes it the diagnostic: if the theme tools are missing, this tool still answers, and its answer explains why.
Get the POM Theme status and tell me whether the theme tools are available.
What it returns
| Field | Meaning |
|---|---|
available |
Whether the other theme tools are registered |
stylesheet |
The active theme's directory |
template |
The parent theme's directory |
version |
The active theme's version |
pom_template_dir |
The theme path constant, if defined |
framework_disk |
Whether the framework's file helper is loaded |
assets_helpers |
Which asset generation functions exist |
available has four conditions
It is true only when all of these hold:
- The active theme, or its parent, is
pom. - The theme's directory constant is defined.
- The framework's disk helper class is loaded.
- The theme's defaults helper function exists.
The remaining fields report each condition separately, which is what makes a failure diagnosable rather than mysterious.
A stylesheet of pom with available false means the theme is active but something in its framework did not load — a plugin conflict, a partial update, or a deployment that copied files without the framework. That is a very different problem from "the wrong theme is active", and this response distinguishes them.
Child themes are handled
available accepts a child theme whose parent is pom. So stylesheet may be your own child theme name while template is pom, and the tools still work.
If both are something else, POM Theme is not in use here, and no amount of configuration will register the tools.
assets_helpers predicts what a rebuild will do
Two functions are reported. pom_theme_generate_assets uses the full one if present and falls back to the CSS-only one otherwise.
So this field tells you, before you call it, whether a rebuild will regenerate CSS and JavaScript or only CSS.
Run it first on any unfamiliar site
Theme work assumes a great deal about what is installed. One call establishes it:
Get the POM Theme status, then list the settings schema.
If available is false, stop there. Attempting the other tools produces pom_ai_mcp_unknown_tool, which reads like a client problem and is not one.
It reads nothing sensitive
The response is theme identity and capability detection — no settings values, no content, no credentials. pom_template_dir is a server path, so treat it as you would any path when sharing diagnostics. See Safe support information.
Common problems
| Symptom | Cause |
|---|---|
pom_ai_mcp_forbidden |
Missing edit_theme_options |
available is false, stylesheet is not pom |
A different theme is active |
available is false, stylesheet is pom |
The framework did not load; check the other fields |
pom_template_dir is empty |
The theme constant is not defined |
framework_disk is false |
The POM framework is not loaded |
| Other theme tools are missing | Expected when available is false |