Candor Finance

Returns an explicitly scoped analytical snapshot built from the requested snapshot datasets and filters, in one response. Use when an analysis needs several datasets together, such as a spending review across accounts. Only datasets declared as snapshot datasets in the Candor schema are available. Dataset reads are recorded in private action history; financial records are not changed.

candor_snapshot

Saves exactly five unique dashboard panels as the workspace Overview and returns the saved configuration. Use when the user asks to change which panels their Overview shows. Repeating a request with the same idempotency_key replays the original result instead of saving again. When the account's access has lapsed, it returns an access recovery response instead of saving.

candor_configure_overview

Returns one typed Candor object, or the result of one GET operation in the Candor API. Use when one known object or published read operation answers the question. Operation-specific arguments follow that operation's published contract (API reference: https://candor.money/developers). The full response returns in this tool result. The read is recorded in private action history; financial records are not changed.

candor_get

Returns computed comparisons for spending, income, recurring payments, account terms, and investment positions, with basis handles and coverage caveats. Use when the user asks how spending, income, recurring payments, account terms, or holdings changed between periods. Spending and income compare recorded posted totals across inclusive since/until and comparison_since/comparison_until ranges; without ranges, the last complete UTC calendar month is compared with the month before, and the response states both ranges. limit trims the items returned without changing the comparison. When source history is incomplete or evidence is capped, spending and income comparisons are withheld. The read is recorded with its reason and does not change the opening checkpoint, seen activity, attention items, or due notes.

candor_changes

Returns Candor API contracts, not financial records. Use when a dataset's filters or an operation's arguments are not already known. With no selector it returns the workspace schema index; dataset returns one dataset's fields, filters, and coverage contract; operation returns one operation's accepted arguments, input schema, and call shape; query searches the operation catalog, with limit up to 10 (default 10). dataset, operation, and query are mutually exclusive. Workspace and dataset schema reads are recorded in private action history; catalog searches and operation descriptions are local lookups. API reference: https://candor.money/developers

candor_schema

Opens the user's Candor workspace and returns what changed since the last processed opening, the current financial position, approved budgets and goals, saved agent context, and current attention items such as due notes, budget or goal drift, upcoming payments, and coverage gaps. Use when starting or resuming work on the user's finances. mode=pulse returns a compact inspection signal without a checkpoint. The default opening returns a checkpoint candidate and an open.acknowledge action in next_actions that marks the opening as processed. The read is recorded in the workspace's private action history; financial records are not changed. Return workspace context, financial position, approved state, new activity, factual attention, and executable next actions. Reading does not advance the shared checkpoint. The checkpoint for this opening is data.new_since_checkpoint.checkpoint_candidate; the same value is carried as args.checkpoint on the open.acknowledge entry in next_actions, so find that entry by command rather than by position. After processing this opening, acknowledge that exact checkpoint to mark activity as seen; acknowledgement does not resolve attention or due notes.

candor_open

Previews one POST operation in the Candor API and returns the proposed result without applying it. Use when the user wants to see what a change would do before it is saved. Arguments follow the operation's published contract (API reference: https://candor.money/developers). Previews are recorded in private action history; the proposed changes are not applied and financial records are not changed.

candor_preview

Returns one page of rows from a declared Candor financial dataset, such as transactions or accounts, filtered by the supplied arguments. Use when an answer needs individual records, such as specific transactions, balances, or holdings. Results use limit and cursor pagination; each cursor is bound to the filters of the page that issued it, and the call for the next page is listed in next_actions. The full page returns in this tool result. The read is recorded in private action history; financial records are not changed. Run one bounded query against a declared financial dataset. Inspect the selected dataset schema for accepted filters and defaults; omitting filters uses those defaults. Cursor-paginated results keep records, calculations, and pagination under data.page. Calculations cover exactly the returned records, not later pages or the full workspace. Follow next_actions for the exact continuation, preserving the query filters.

candor_query

Refreshes data from financial accounts the user has already connected to Candor. Use when balances or transactions are older than the question needs. Connecting, reconnecting, or disconnecting an institution happens only in the Candor web app. Connected account details are in the accounts dataset.

candor_connections

Returns one Candor dashboard panel or the saved Overview as text context, structured panel data, and a View in Candor link. Use when the user wants to see a Candor chart or dashboard panel. Hosts that support MCP Apps also render the panel with Candor's dashboard renderer. Panel reads are recorded in private action history; financial records are not changed.

candor_visualize