Get application setup proposal
get_application_setup_proposalRead the setup Ankra generated for an Application before anything is deployed: the detected language and framework, the setup pull request it opened, whether it generated a database (a CloudNativePG PostgreSQL cluster) and which manifest declares it, and the deploy option contract of record from the repository's .ankra/ankra.yaml - the same options the deploy form renders and the deploy endpoint validates inputs against. negotiable_options lists exactly what revise_application_setup can change. The contract and database members each carry a three-valued status: 'recorded' (read successfully), 'absent' (recorded and genuinely not there) or 'unknown' (nothing recorded, or the recorded file could not be read) - never report an 'unknown' as though Ankra proposed nothing. Read this before revising. Read-only.
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>"
},
"name": "get_application_setup_proposal"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| application_id | Yes | The Application's id. |