List what can be priced and named
list_cost_building_blocksEverything the estimator can be asked about, by name: a lookup, not an answer.
Use this when you need the exact ids that `estimate_cost`,
`compare_architectures` and `where_can_this_run` take and do not have them.
They reject any name not listed here. `describe_workload` does not need it:
it takes the user's plain words.
Not as the answer to a question: it prices nothing and applies no
requirement. One call per conversation is enough. Narrow it with `of`
(`components`, `capabilities`, `archetypes`, `drivers`, `constraints`,
`regions`), then go straight on to the tool that answers. Each entry carries
the exact shape to pass it back in. Do not stop to ask the user for detail
that the next tool defaults or that you can state as an assumption.
If what the user described is not in here, say so plainly and say what IS
covered. An estimate assembled from the nearest parts, presented as the
thing they asked about, is worse than no estimate.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "list_cost_building_blocks"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| of | No |