corecluster_ capacity_ check
Check CoreCluster capacity.
When to use it
Whether a set of new sites and environments (and the removal of others) would fit a CoreCluster or a package, before anything is created. Nothing is reserved.
Automatic upgrades: on a CoreCluster whose company turned them on, a create that would take the cluster past 90 % of its package first buys the smallest add-on raise that makes room (or, when add-ons cannot, the next package), within the company's monthly limit, and goes ahead. Each upgrade stays on the monthly bill until it is changed back. Over the limit it is refused with capacity_blocked, naming the limit. See corestack_company_auto_upgrades_get. For such a CoreCluster this check answers grows: true and a warning instead of a capacity_blocked entry (on its own package, not a package what-if).
Ask for it
Using the Corefinity MCP server, call corecluster_capacity_check with cluster_id 812, sites [{"platform":"wordpress","tier":"M"}]. (Check CoreCluster capacity.) Tell me what it returned.Inputs
Your CoreCluster; leave out to check a package before a cluster exists. At least 1.
New environments: {platform, tier} rows. Up to 50 items.
Fields of each item
Up to 32 characters.
Up to 32 characters.
A package key (corestack_packages_list): project onto this package instead. Up to 64 characters.
Without cluster_id only: the region the cluster would be in. Up to 16 characters.
Ids of sites on the cluster to leave out of the projection.
New sites: {platform, tier} rows (at most 50 rows across sites and environments).
Fields of each item
Up to 32 characters.
Up to 32 characters.
Example call
{
"name": "corecluster_capacity_check",
"arguments": {
"cluster_id": 812,
"sites": [
{
"platform": "wordpress",
"tier": "M"
}
]
}
}If it is refused
| Reason | What to do |
|---|---|
invalid_arguments | The 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_mismatch | The object does not exist or the token may not see it. Check the id. |
scope_required | The token lacks a scope this call needs. Open the link in the answer to add it, then call again. |
pin_refused | The 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_limited | Too many calls. Wait for the number of seconds the answer names. |
temporarily_unavailable | The Control Panel could not answer just now. Nothing was started; try again shortly. |
internal_error | Something went wrong on our side. Quote the trace id to support. |