Triggers
Design a trigger
Turn a commercial rule into a testable tool condition.
Write the intended behavior in plain language before opening the editor.
Use this worksheet:
When [tool and condition], require [payment type, amount, and currency], then tell the user [clear result].
Make the rule specific
- Select an existing discovered tool.
- Use the smallest condition that expresses the intended rule.
- Define exactly what counts toward any allowance.
- Choose an amount and currency the MCP Owner can support.
- Write a message that explains what the user is buying.
Avoid ambiguity
Do not rely on a tool description alone to define the commercial rule. Record the condition explicitly and test its boundaries.
For a quota, write down:
- The included amount.
- The usage unit.
- When usage should count.
- What happens immediately before and after the limit.
For input-based rules, use only fields present in the current discovered tool schema. Refresh tools first if the upstream contract changed.