CorefinityCorefinityDocs
Open the Control PanelControl Panel
Varnish · 1 of 12

corestack_varnish_get

Show a site's Varnish.

Scope readNo secrets returned
On this page

When to use it

Read a Magento 2 row's Varnish full-page cache before changing anything: whether it is offered and on, the version in use and the versions this Magento allows, the cache size, whether Magento is configured for it, the purges left this hour and the VCL revision. Varnish runs in front of every Magento 2 site and environment on CoreStack and CoreCluster, on by default; access control (HTTP auth, the firewall, maintenance) always runs before the cache.

What the answer tells you:

  • offered: false on a row Varnish cannot run on yet (for example after this site's platform update).
  • enabled and version: on or off, and the Varnish version (a row switched off keeps its version for the next switch-on).
  • options[]: every version with allowed (what corestack_varnish_version_change and corestack_varnish_set accept for this Magento), recommended (the version Adobe certifies for the installed Magento patch), reason (why a version is not allowed), status (supported, lts, eol, prerelease) and eol_date. An eol target needs acknowledge: ["eol"].
  • memory_mib and storage_mib: the cache's share of the site's memory and its page storage. It comes from the Redis full-page cache share (Magento's full-page cache moves to Varnish), never from PHP.
  • magento_config.state: varnish (Magento sends its pages and purges to Varnish), builtin (Magento's own cache), needs_repair (repair with corestack_function_run and the function magento_varnish_config) or pending_code (configured at the first deployment).
  • purge: remaining_this_hour of the ten an hour per site, available_in seconds when none is left, and the last purge (origin says who or what sent it: panel, api, mcp, deployment, magento and so on).
  • vcl: the custom VCL revision and the one applied (corestack_varnish_vcl_get has the text); pending: a change waiting for the maintenance window.
  • site: the row's id, domain and environment name.

The Varnish App (hit ratio, requests, memory and purges as charts, with a Flush cache sheet) opens from this tool in clients that show apps; corestack_varnish_stats has the same series as data.

Ask for it

Prompt
Using the Corefinity MCP server, call corestack_varnish_get with site_id 4211. (Show a site's Varnish.) Tell me what it returned.

Inputs

site_idintegerRequired

The row, a Magento 2 site or one of its environments. At least 1.

Example call

tools/call
{
  "name": "corestack_varnish_get",
  "arguments": {
    "site_id": 4211
  }
}

If it is refused

ReasonWhat to do
varnish_not_offeredThe row is not a Magento 2 site.
invalid_argumentsThe arguments do not match the tool's input schema, or the Control Panel refused a field. Fix the fields named in the answer and call again.
tenant_mismatchThe object does not exist or the token may not see it. Check the id.
scope_requiredThe token lacks a scope this call needs. Open the link in the answer to add it, then call again.
pin_refusedThe grant is limited to chosen clusters, sites or environments, and this call is outside them. Open the link in the answer to widen it.
rate_limitedToo many calls. Wait for the number of seconds the answer names.
temporarily_unavailableThe Control Panel could not answer just now. Nothing was started; try again shortly.
internal_errorSomething went wrong on our side. Quote the trace id to support.

The same task elsewhere

Was this helpful?
Open in ClaudeOpen in ChatGPT