Estimate application cost
estimate_application_costEstimate what a change to an Application would cost per month before making it. change is one of replicas, resources, park, promote, new_environment or database. replicas, resources, park and promote change an existing deployment and need its cluster_id and namespace; replicas needs replicas, resources needs cpu_request or memory_request. An answer with priced false names why in unpriced_reason and is not a cost of zero. Changes nothing.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"application_id": "<application_id>",
"change": "<change>"
},
"name": "estimate_application_cost"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| change | Yes | The kind of change to estimate. | |
| service | No | database only: the managed service engine; PostgreSQL when omitted. | |
| replicas | No | replicas only: the new replica count. | |
| namespace | No | The namespace of the deployment the change applies to. | |
| cluster_id | No | The cluster of the deployment the change applies to, or the cluster a new environment or database would run on. | |
| parameters | No | database only: the plan parameters, names to integers. | |
| cpu_request | No | resources only: the new CPU request, as Kubernetes spells it (500m). | |
| application_id | Yes | The Application's id. | |
| memory_request | No | resources only: the new memory request, as Kubernetes spells it (512Mi). |