pom://theme/settings-schema: entry point, not a schema dump

This resource deliberately returns a small JSON pointer:

{
  "description": "Use pom_theme_list_settings_schema for the live POM Theme settings schema.",
  "tool": "pom_theme_list_settings_schema"
}

It exists so resource-driven clients can discover the correct live tool without embedding an outdated copy of every POM Theme setting.

Why the schema is a tool

Theme settings are dynamic. Available sections, tabs, fields, labels, types, choices, defaults, dependencies, and current initialization state can vary with the active POM Theme version and site configuration. pom_theme_list_settings_schema can narrow that live data; a static resource would quickly become too large and stale.

Correct workflow

1. Read this resource once to discover the tool.
2. Call pom_theme_list_settings_schema, filtering to the relevant setting group where possible.
3. Read the current value with pom_theme_get_settings_values.
4. Check the field type, allowed choices, and dependency.
5. Use pom_theme_update_setting with dry_run: true.
6. Apply only if the field is on the MCP write allowlist and the user approved the change.
7. Read the value back and verify the public result.

Schema visibility and writability are separate. Most live POM Theme fields are readable but not writable through MCP by default. Never route a denied field through wp_update_option or a generic theme-mod operation.

Related guides: list the live settings schema, update a setting, and POM Theme authorization.