Action dispatchers
The problem
Simon exposes tools that the AI agent can call. But the more tools there are, the wider the choice surface becomes for the model — and the higher the risk of selecting the wrong one.
Yet business actions number in the hundreds: bank reconciliation alone brings together more than twenty. If each action were a distinct tool, the agent would have to choose from an endless list of often similar names, on each call. Selection errors would be frequent.
The solution: one dispatcher per domain
Each business domain exposes a single tool, which routes internally to its N actions. The agent therefore sees only about twenty tools — one per domain — instead of a hundred flat actions.
The benefits
It is first a reduced surface for the model. It chooses the domain (bank reconciliation, manual entries, lettering…), then the action within it — a more natural path than a flat choice among a hundred tools.
It is next self-documentation. Discovery tools let the agent list the actions of a domain and their parameters without external documentation.
It is finally unified validation: each action has its validation model. The dispatcher cleans and validates the parameters before reaching the business logic, and returns clear messages rather than technical errors.
The main domains
The contract registry exposes about 18 domains. Here are the most used (the number of actions is indicative and evolves):
| Domain | Actions | Coverage |
|---|---|---|
| Bank reconciliation | 20+ | Auto/manual matching, multi-document groups, direct categorization |
| Manual entries | 15+ | Manual journal entries, closing, depreciation, provisions, adjustments |
| Bank | 16 | Missing documents, receipts, accounts, balances, transactions |
| Qualification | 12 | Deductibility, patterns, rules, VAT |
| Documents | 11 | Confirmation, classification, third parties, VAT, drafts |
| FEC import | 11 | Import declaration, mapping, execution, documents, fixed assets |
| Commitments | 10 | Schedules, realization, payment matching |
| Tax | 10 | Profile, regime, preparation and submission of returns, amendments |
| Accounting | 9 | Validation, reversal, rejections, closing rates |
| Mileage allowances | 9 | Vehicles, calculation, DGFIP scale |
| Lettering | 8 | Invoice/payment association, partial lettering |
| Entities | 5 | Create, correct, merge, delete, reclassify |
| Periods | 5 | Opening, closing, external management |
| Invoicing | 4 | Create, issue a credit note, update, list |
| Cash | 3 | Position, projection, comparison |
| Cancellation | 2 | List and cancel the latest actions |
The trade-off
The dispatcher adds a level of indirection: the agent must know the name of the action in addition to that of the tool. In practice, the skills lift this difficulty — each guided procedure documents the exact actions to call, in the right order.