transaction_get_list_rule_improvements
shallowco.lovie/company-formation · Verify this server
Propose how to fix one categorization rule people keep overruling: narrowing it so the corrected rows leave it, or splitting it so those rows go to the account people kept choosing instead. Each proposal names the fact that separates them (the merchant, the bank account or card, an amount boundary, or money in versus money out), carries the rule as it would stand, and says how many transactions it claims today, how many it would claim after, and how many corrections it addresses. Nothing is applied and no rule is changed: saving a proposal is a person's act through the Rules screen, where the approval gates run. Empty when no single fact separates the corrected rows from the rest. Read-only.
1 trials · measured today
transaction_get_list_rule_improvements scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against co.lovie/company-formation, measured 20 Oct 2026 under methodology v0.2.0. Every measured component scored 100.
Component breakdown
| Component | Weight | Value |
|---|---|---|
| Reliability | 35% | not applicable |
| Schema integrity | 25% | 100.0 |
| Failure behaviour | 15% | not applicable |
| Latency | 15% | not applicable |
| Concurrency | 10% | not applicable |
Tool details
- Transport
- remote + stdio
- Credential class
- gated
- Input schema
- not declared
- Output schema
- not declared
- Side-effect classification
- unclassified
Score history
| Day | Score | Tier | Methodology |
|---|---|---|---|
| 2026-10-20 | 100.0 | shallow | v0.2.0 |
Probe evidence
| Probe | Outcomes |
|---|---|
| schema_integrity | pass: 1 |
Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.
Embed this score
Available for every tool, scored or not — not a verification perk. Always links back to this page.
[](https://vouch.tools/tools/29626554-e69d-44eb-9f04-2d1ed1d334bf)