Client Intake Function Call Schema Audit

Role: Principal Legal Tech Architect with 12+ years optimizing automated intake workflows.

Context

• Practice domain: {{practice_area}}
• Firm operating scale: {{firm_size}}
• Master CRM and billing system: {{target_crm_database}}
• Conflict checking API schema: {{conflict_api_spec}}
• Regulatory compliance benchmark: {{compliance_standard}}
• Endpoint authentication scheme: {{authentication_type}}

Task

Produce a comprehensive verification checklist that audits JSON schema definitions, parameter constraints, and safety boundaries for autonomous client conflict-checking function calls within professional legal services.

Method

1. Parse the provided {{conflict_api_spec}} against {{target_crm_database}} integration requirements.
2. Evaluate parameter definitions for required versus optional client entity attributes.
3. Verify strict type constraints, regex patterns, and enumeration bounds for corporate identifiers.
4. Audit function descriptions for disambiguation markers that prevent inappropriate tool selection.
5. Design deterministic validation rules preventing malformed or malicious payload injections.
6. Verify compliance with {{compliance_standard}} data residency, masking, and field exclusion rules.
7. Establish authentication header and token lifecycle validation under {{authentication_type}}.
8. Structure automated failover criteria for handling database lockouts and API timeouts.

Constraints

• MUST enforce zero tolerance for unescaped string injection in tool parameter schemas.
• MUST validate every schema property against {{compliance_standard}} privacy constraints.
• All checklist items must follow an actionable imperative verb structure.
• Do not include generalized software engineering advice unrelated to function calling.

Output format

1. Schema Definition Checklist (5 items with Pass/Fail criteria)
2. Parameter & Type Safety Checklist (4 items with validation rules)
3. Error Handling and Fallback Checklist (4 items with trigger conditions)

Self-review

• Confirm all 6 context variables are directly addressed in checklist items.
• Ensure each checklist item includes concrete technical parameters rather than generic advice.
• Verify output strictly adheres to the 3 named sections without preamble.