Tool & function calling
AuraScore 83/100

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.

Template

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

  1. Enumerate the exact API actions required by the agent across {{asset_classes}} lifecycle management.
  2. Construct rigid tool-calling schemas containing explicit slippage, limit, and sizing parameters.
  3. Integrate pre-execution validation checks matching {{risk_thresholds}} directly into tool argument filters.
  4. Map deterministic translation logic between LLM function arguments and {{order_management_system}} payloads.
  5. Design routing pathways for order confirmation receipts over {{settlement_network}}.
  6. Formulate error interceptors for market data divergence or stale quote exceptions.
  7. 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_dispatch schema contains strict parameter typing for price and volume.
  • Verify that risk threshold validation occurs strictly upstream of order submission.
AuraScore breakdown
83/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness5/5 · Strong

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

ai-agents
agents-tool-calling
financial-services
wealth-management
function-calling
trading