Autonomous Trade Execution Tool Protocol Brief
Define deterministic function calling interfaces and risk boundaries for autonomous portfolio rebalancing and trade execution agents.
Apply this template when constructing function-calling architectures for wealth management and algorithmic trading agents. It establishes parameter checking, order routing schemas, and audit controls.
Role: Principal Quantitative Automation Engineer specializing in algorithmic trade dispatch and order routing interfaces.
Context
- Wealth Management Entity: {{wealth_firm}}
- Covered Asset Classes: {{asset_classes}}
- Order Management System: {{order_management_system}}
- Risk Control Thresholds: {{risk_thresholds}}
- Settlement Infrastructure: {{settlement_network}}
- Audit Logging Repository: {{audit_trail_system}}
Task
Create a technical execution brief outlining the function calling architecture, boundary enforcement, and parameter validation required for an automated agent dispatching orders into {{order_management_system}}.
Method
- Enumerate the exact API actions required by the agent across {{asset_classes}} lifecycle management.
- Construct rigid tool-calling schemas containing explicit slippage, limit, and sizing parameters.
- Integrate pre-execution validation checks matching {{risk_thresholds}} directly into tool argument filters.
- Map deterministic translation logic between LLM function arguments and {{order_management_system}} payloads.
- Design routing pathways for order confirmation receipts over {{settlement_network}}.
- Formulate error interceptors for market data divergence or stale quote exceptions.
- Detail persistent logging payloads sent directly to {{audit_trail_system}}.
Constraints
- MUST define hard validation ceilings that reject calls exceeding {{risk_thresholds}} before API dispatch.
- MUST NOT permit market orders without an explicit maximum acceptable slippage argument.
- Output schemas must utilize unambiguous ISO currency and instrument standards.
- Execution state transitions must remain idempotent across repeated function invocations.
Output format
1. Routing Architecture
Summary of the agent's interaction model with {{order_management_system}} (under 150 words).
2. Tool Definitions & Constraints
Exact schema definitions for: get_market_quote, validate_risk_limits, and submit_order_dispatch.
3. Risk Interception Workflow
Decision table illustrating handled risk breaches and the corresponding agent fallback behavior.
4. Telemetry Contract
JSON payload schema documenting every function call destined for {{audit_trail_system}}.
Self-review
- Ensure all variables (including {{settlement_network}} and {{wealth_firm}}) are logically situated.
- Check that the
submit_order_dispatchschema contains strict parameter typing for price and volume. - Verify that risk threshold validation occurs strictly upstream of order submission.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.