Client Discovery ERP Function Calling Architecture Brief
Design automated diagnostic tool-calling workflows connecting advisory agents to client enterprise resource planning systems.
Use this template when setting up real-time telemetry and ERP data retrieval agents for management consulting discovery. It produces an integration brief specifying function endpoints, parameter guardrails, and query rate controls.
Role: Enterprise Architecture Advisory Lead specialized in agentic integrations and enterprise data orchestration.
Context
- Client Account: {{consultancy_client}}
- Target Core System: {{primary_erp_system}}
- Diagnostic Metric Scope: {{diagnostic_kpis}}
- Authentication Standard: {{auth_protocol}}
- Response Latency SLA: {{latency_sla}}
- Exception Policy: {{error_handling_policy}}
Task
Develop an enterprise function-calling integration brief that allows autonomous discovery agents to inspect financial and operational metrics within client systems safely, accurately, and within corporate security boundaries.
Method
- Enumerate the precise read-only API endpoints within {{primary_erp_system}} needed to calculate {{diagnostic_kpis}}.
- Translate business metric discovery inquiries into a modular suite of callable agent tool definitions.
- Construct parameter parsing rules that enforce temporal bounding, fiscal quarter indexing, and currency normalization.
- Design secure token negotiation and context passing using the constraints of {{auth_protocol}}.
- Establish rate limiting, caching, and payload size thresholds to satisfy {{latency_sla}} without exhausting client compute.
- Define deterministic error recovery sequences governed by {{error_handling_policy}} for locked tables or schema drift.
- Map agent invocation routing rules to ensure parallel execution across independent diagnostic sub-queries.
Constraints
- All tool interfaces MUST be strictly read-only with zero mutate, update, or delete privileges.
- Agent function payloads MUST NOT expose raw database connection strings or administrative bearer tokens.
- Each tool definition must cap return datasets to a maximum row count per execution turn.
- Output payloads must use standard ISO formats for timestamps, currencies, and geographic entities.
Output format
- Section 1: Diagnostic Tool Directory (list of 3-5 function signatures with name, purpose, and args)
- Section 2: Security & Authentication Envelope (2-3 concise paragraphs covering credential delegation)
- Section 3: Metric Extraction Routing Matrix (table: KPI, Function Sequence, Output Type, Timeout SLA)
- Section 4: Operational Guardrails & Failure Modes (bulleted list of failure codes and fallbacks)
Self-review
- Check that every listed function aligns strictly with the read-only discovery mandate.
- Confirm that authentication parameters are handled via headers and not passed through prompt text.
- Verify that the total tool suite directly satisfies the extraction needs of all requested diagnostic KPIs.
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.