Skip to main content

Constraints

Constraints are rules that govern valid inputs and valid execution conditions for an operation. In AXAG, constraints are declared as part of the semantic contract — not hidden in client-side validation logic.

Types of Constraints​

Value Constraints​

Rules about individual parameter values:

  • Type constraints: type: "string", type: "number"
  • Format constraints: format: "email", format: "date"
  • Range constraints: min: 0, max: 100
  • Enum constraints: enum: ["draft", "published", "archived"]
  • Pattern constraints: pattern: "^[A-Z]{2}[0-9]{6}$"

Relational Constraints​

Rules about relationships between parameters:

  • Ordering: price_min must be less than price_max
  • Conditional requirement: shipping_address_id is required when delivery_method is "ship"
  • Dependency: payment_method_id requires billing_address_id

These have no machine-readable form in AXAG 1.1. Write them as preconditions and in the description, and enforce them where the operation runs.

Execution Constraints​

Rules about when the operation can execute:

  • Preconditions: State that must be true before execution
  • Rate limits: Maximum invocation frequency
  • Cooldown periods: Minimum time between invocations

Why Declaring Constraints Matters​

Validation rules that exist only in client-side JavaScript are invisible to agents. If a form requires an email format but only validates on blur, an agent has no way to know this until submission fails.

AXAG makes constraints part of the contract, enabling agents to construct valid inputs on the first attempt. Value constraints reach the generated tool's input schema, so a host can often reject a bad value before the call is even made. See Constraints for how each kind is declared.

Next Steps​