Where an architecture is allowed to run, and what that costs
where_can_this_runApply requirements FIRST, then price only the regions that survive.
Use this when the question is WHERE something may or should run (data
residency, a jurisdiction to avoid, near its users, surviving a zone
failure), with or without what it would cost. Not for pricing one region
already chosen: that is `estimate_cost`, or `describe_workload` for a
workload in plain words.
`items` (the `estimate_cost` shape, not empty) and `constraints`
(`[{"constraint": "<id>", "value": "<value>"}]`) take ids from one
`list_cost_building_blocks` call with `of=["components", "constraints"]`,
then come straight here. If a location value is refused, the error lists
the valid values: retry with one of those.
The user does not have to describe the workload first. Location
requirements decide which regions are allowed whatever the architecture,
so pass the smallest one that fits what they said and state it as an
assumption. An architecture requirement (zone failure) applies only to the
components you pass: read `changes` and `unmet`, and never report anything
in `unmet` as met.
Only requirements in the catalogue's `constraints` are checked.
`users_near` narrows to a broad area such as `emea`, not to a latency
figure: for a millisecond target, say plainly that it was not checked.
`options` are allowed regions that price every line, cheapest first.
`cannot_run_this` are allowed but do not sell part of it. `excluded` failed
a requirement, each with the reason. `cost_of_requirements` splits the
premium into location and the architecture changes it forced.
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": {
"items": "<items>",
"constraints": "<constraints>"
},
"name": "where_can_this_run"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| term | No | OnDemand | |
| items | Yes | ||
| regions | No | ||
| constraints | Yes |