intelligence_suggestion_approve
Approve a StrategySuggestion, optionally creating the suggested Strategy.
Closes the PROPOSE loop for MCP-only agents: wraps the same
approve-and-create service logic as the REST
StrategySuggestionViewSet.approve action instead of a manual
suggested_config round-trip through the strategy create tools, which
silently drops the suggestion linkage (StrategySuggestion.created_strategy
/ hive DecisionRecord.suggestion FK provenance). wallet_address is the
caller's own wallet (recorded as approved_by_wallet); when
agent_wallet_id also resolves to a wallet wallet_address controls,
the suggested Strategy is created through the same executor dry-run gate
as every other create path. config_overrides merges over
suggested_config (e.g. a real usd_per_buy). A wallet without a
Turnkey signer still gets the strategy -- paper trade, unsigned tx per
tick. Informational rationale only (rules 5-8); the created strategy still
runs only through the existing engine gates.
Workflow: DECIDE -> EXECUTE step -- the MCP-only closing move for get_strategy_suggestions; pair with backtest_strategy + get_risk_assessment first for the same guardrails any other create path gets.
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": {
"suggestion_id": "<suggestion_id>",
"wallet_address": "<wallet_address>"
},
"name": "intelligence_suggestion_approve"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| caller_id | No | ||
| suggestion_id | Yes | ||
| wallet_address | Yes | ||
| agent_wallet_id | No | ||
| config_overrides | No | ||
| interval_seconds | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||