Pull a spec to build from
pull_specReturns a spec's files, ready to write into a folder and build from: BUILD.md (how to build), spekkr.json (the manifest), spekkr.inputs.json (the person's choices) and the spec files. It checks the choices first and refuses a key the spec does not declare or a value it does not offer. Anything not chosen keeps the spec's default.
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": {
"id": "<id>"
},
"name": "pull_spec"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The spec's id, like username/name. | |
| choices | No | The person's choices, by key from manifest.customize: any text for a setting, true or false for an option (on and off are taken too), one of its choices for a swap. For example {"database": "sqlite", "teams": false}. The answer and spekkr.inputs.json write an option as true or false, as the manifest writes its default. |