Documentation
detect_recurring
detect_recurring MCP tool reference, parameters, return type, and safety hints.
What it does
Detects recurring activity in the local Clovis ledger.
(months?: number, year?: number | null, month?: number | null, min_occurrences?: number, amount_tolerance_pct?: number, account_id?: string | null) => Array<Record<string, unknown>>Read-only. This is appropriate for inspection, reporting, diagnostics, and first-pass agent answers.
When to use it
Use this section to decide whether the tool fits the user request before calling it.
Before calling
Agents should gather these facts or confirmations first.
No required inputs are needed, but date, status, asset, and account filters should still be explicit when the user cares about scope.
Parameters
Required inputs are marked clearly. Optional inputs can usually be omitted unless the workflow needs them.
monthsoptionalNumeric value used by this workflow.
Default: 6yearoptionalFour-digit year.
Default: nullmonthoptionalMonth number from 1 to 12.
Default: nullmin_occurrencesoptionalMinimum repeated occurrences required before a pattern is reported.
Default: 2amount_tolerance_pctoptionalPercent difference allowed when matching similar amounts.
Default: 5account_idoptionalLedger account id or resolvable account reference.
Default: nullAgent call shape
Use the exact tool name and pass arguments as structured JSON through the MCP client.
detect_recurring
Copy this shape into agent instructions, evals, or MCP client tests.
{
"tool": "detect_recurring",
"arguments": {}
}