Deterministic Schedule III statements for Indian companies: trial balance in, Excel workbook out.
| Endpoint | https://app.datavrn.com/api/mcp (streamable-http) |
|---|---|
| Registry version | 1.0.0 |
| Now | 67 tools · grade F (6) · pin ts_3d0a4812589647306002d706f6444183 · protocol 2025-06-18 |
| First / last listed | 2026-10-27 02:31 UTC / 2026-10-27 02:31 UTC |
| Grade over time | 2026-10-27: F (6), 67 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: list_clients create_client upload_trial_balance get_upload set_header_row confirm_column_mapping ingest_upload list_periods get_schedule3_workspace list_grouping_suggestions confirm_groupings save_adjustments save_py_values save_asset_movements save_provision_movements save_reserves_movements save_share_capital save_statement_settings save_disclosures declare_capture_na confirm_capture_review revoke_capture_declaration copy_capture_declarations save_partner_capital get_partner_capital save_accounting_policies save_regulatory_affirmations list_statement_policy_choices get_finalise_readiness finalise_statement get_comparative_source_state assert_previous_year_no_activity generate_schedule_iii get_job list_snapshots get_workbook_download create_upload_link get_upload_link_status get_statement_figures get_statement_notes get_tb_rows get_pending_work list_allocation_runs get_allocation_account_figures get_allocation_target_figures get_spreading_reconciliation list_budgets get_budget get_variance_report get_consolidated_statements list_cost_centres create_cost_centre list_profit_centres create_profit_centre list_account_mappings confirm_centre_mappings list_reporting_lines confirm_reporting_lines get_setup_status list_replacements preview_replacement_restore restore_replacement list_chart_rebaselines preview_chart_rebaseline confirm_complete_chart verify_connection get_help
list_clients | List the entities (companies) this credential can work with. Call this first to resolve the client_id every other tool needs. Returns each entity id and name. params: none |
create_client | Create a new entity (company) in the organization. Requires a Manager-role key. Use only when the user explicitly asks to set up a new entity; show them the name you will create first. params: name*, business_model_code |
upload_trial_balance | Stage a Trial Balance spreadsheet (xlsx or csv, max 4 MB) for an entity by INLINING its bytes as base64. This path is ONLY for programmatic callers (a script, Claude Code, an automation) that already have the raw file on disk. If a HUMAN has the file — e.g. they attached it to this chat — do NOT use this tool and do NOT base64-encode the file: call create_upload_link instead and give them the link params: client_id*, file_name*, file_base64*, format, source |
get_upload | Read an upload session: status, detected header row and columns, the confirmed mapping (if any), and the stored validation outcome. Use to check what a staged upload still needs. params: upload_id* |
set_header_row | Correct the detected header row of a staged upload (1-based). Only needed when get_upload/upload_trial_balance shows the wrong row was detected. params: upload_id*, header_row* |
confirm_column_mapping | Confirm the column→field mapping for a staged upload and run validation. Returns the full validation result (row counts, warnings, blocking issues). Mapping suggestions are never auto-applied — pass exactly the mapping your user approved. Review any warnings with your user before ingesting. params: upload_id*, mapping*, options, save_as |
ingest_upload | Commit a validated upload into the entity’s books. This is a TWO-CALL approval: if the upload has any warnings, or would permanently delete existing trial-balance rows for a period it covers, the first call writes NOTHING and refuses with every warning, the exact record counts, and a short-lived removal_token. Show your user every warning and both counts, get their explicit go-ahead, then resend t params: upload_id*, acknowledge_warnings, acknowledged_state_digest, confirm_merges, removal_token, removal_count |
list_periods | List the reporting periods a Schedule III statement can be prepared for (periods with a live Trial Balance). Returns period ids for get_schedule3_workspace, save_py_values, and generate_schedule_iii. params: client_id* |
get_schedule3_workspace | THE state tool: grouping progress, every required capture answer, generated/finalised versions, finalisation blockers, and bounded per-version control summaries. Report generation never marks capture complete. Exception output is rule/severity/count only — no account names or amounts. Call this to know what is left before finalising. params: client_id*, template_id*, period_id* |
list_grouping_suggestions | List ungrouped accounts with DETERMINISTIC grouping suggestions (curated rules + name/group-path matching — no AI is involved; Datavrn never applies a suggestion itself). Paginated. Each row carries a reason and a confidence tier: present them to your user GROUPED BY CONFIDENCE, and call out low-confidence and balance-bearing rows for individual attention — a single blanket approval is not a revie params: client_id*, template_id*, period_id*, limit, offset, include, confidence, has_balance |
confirm_groupings | Persist USER-approved account→line groupings. Omitted accounts stay unchanged. Only explicit leaf_code:null clears a saved grouping. When clearing a saved grouping, use the current grouping_version from list_grouping_suggestions. An actual clear first returns an approval request; nothing changes then. Resend the unchanged request with the approval details to proceed. Clearing an already-unclassifi params: client_id*, template_id*, decisions*, grouping_version, removal_token, removal_count |
save_adjustments | Save one balanced adjustment journal entry (debits = credits) as an atomic whole entry. Creating a new entry proceeds immediately. Replacing an existing entry first returns an approval request; nothing changes then. Review the existing entry in the Schedule III workspace, then resend the unchanged request with the approval details to proceed. Amounts are strings in rupees. params: client_id*, template_id*, period_id*, entry_no*, lines*, removal_token, removal_count |
save_py_values | Override the prior-year comparative for one or more statement lines with an audited figure. The prior-year column fills itself automatically from the previous year's Trial Balance read through the current groupings, so use this only when the audited financial statements differ from that figure (for example appropriations booked outside the ledger), or when there is no previous-year Trial Balance t params: client_id*, template_id*, period_id*, values* |
save_asset_movements | Save fixed-asset movements (additions, deletions, depreciation charge, depreciation on deletions) per gross-block line for the PPE schedule. params: client_id*, template_id*, period_id*, movements* |
save_provision_movements | Upsert provision movements (additions, amounts utilised) per provision line. Omitted saved lines stay unchanged. To remove selected saved lines, pass remove_leaf_codes; to remove the entire saved set, pass clear_all (never both). An actual removal first returns an approval request; nothing changes then. Review current movements in the Schedule III workspace, then resend the unchanged request with params: client_id*, template_id*, period_id*, movements*, remove_leaf_codes, clear_all, removal_token, removal_count |
save_reserves_movements | Upsert reserves/equity movements (transfers in/out, dividends, other changes) per reserves line. Omitted saved lines stay unchanged. To remove selected saved lines, pass remove_leaf_codes; to remove the entire saved set, pass clear_all (never both). An actual removal first returns an approval request; nothing changes then. Review current movements in the Schedule III workspace, then resend the unc params: client_id*, template_id*, period_id*, movements*, remove_leaf_codes, clear_all, removal_token, removal_count |
save_share_capital | Save the share-capital reconciliation for the period: the opening share count, the shares issued and bought back during the year, and the amount issued and the amount bought back. params: client_id*, template_id*, period_id*, opening_shares*, shares_issued*, shares_bought_back*, amount_issued*, amount_bought_back* |
save_statement_settings | Save statement settings (rounding unit, signatory details, company information used on the statement face). params: client_id*, template_id*, period_id*, entity_name_override*, cin*, registered_office*, unit_label*, unit_divisor*, weighted_equity_shares*, weighted_potential_equity_shares*, weighted_equity_shares_py*, weighted_potential_equity_shares_py*, equity_face_value*, font_name, entity_class, include_cfs, suppress_nil_lines, rounding_off |
save_disclosures | Save the notes/disclosures sections the user provides for the statement. Some of these sections IDENTIFY PEOPLE BY NAME — shareholders, promoters and related parties — so send only what your user has given you, exactly as they gave it. SECTIONS YOU DO NOT SEND ARE LEFT ALONE. Send only the sections you are changing; every other section keeps exactly what is saved. Within a section you DO send, the params: client_id*, template_id*, period_id*, payload*, removal_token, removal_count |
declare_capture_na | Record that a capture section had NOTHING to report this period, DOES NOT APPLY to this entity, or that this is the entity’s FIRST YEAR (previous-year figures only). These are three different statements and are not interchangeable: "nothing this period" means the section applies but had no activity; "does not apply" means it never applies to this entity at all. This is your user’s professional ass params: client_id*, template_id*, period_id*, capture_kind*, reason_code*, note, on_behalf_of |
confirm_capture_review | Record your user’s confirmation that they have REVIEWED a whole section and it is complete — the entire previous-year comparative column, or the entire disclosure set. A review confirmation is your user’s professional assertion, recorded as authorised by them. Before calling this, show them what you are confirming — the whole comparative, or the whole disclosure set — and get their explicit go-ahe params: client_id*, template_id*, period_id*, capture_kind*, reason_code*, note, on_behalf_of |
revoke_capture_declaration | Withdraw a recorded capture answer or review confirmation. What happens next depends on what answers the section: withdrawing a “nothing to record”/“does not apply” answer or a review confirmation makes Statement readiness show the section as UNANSWERED again; withdrawing a leftover earlier note from a section that is answered by its saved rows removes the record and the section STAYS answered. A params: client_id*, template_id*, period_id*, capture_kind*, on_behalf_of |
copy_capture_declarations | Copy the previous period’s "nothing this period" and "does not apply" answers into this period, for sections that have no answer yet. It NEVER copies a review confirmation — a review is about this period’s content and cannot be inherited. Last period’s answer is not evidence about this period: list what it would copy to your user, section by section, and get their go-ahead before calling it. Answe params: client_id*, template_id*, period_id*, on_behalf_of |
save_partner_capital | Save the partner or owner capital schedule for an LLP or other non-corporate entity — Note 3a (capital account) or Note 3b (current account), one section per call. Send the COMPLETE schedule for the section you name: anyone you leave out is removed, and a renamed partner reads as one removal plus one addition. If your request would remove anyone, would change the figures of a partner who stays — i params: client_id*, template_id*, period_id*, account_kind*, rows*, removal_token, removal_count, on_behalf_of |
get_partner_capital | Read the partner or owner capital schedule currently on file — Note 3a and Note 3b. THIS RETURNS PEOPLE’S NAMES, along with each person’s profit-sharing ratio and amounts. Call it before save_partner_capital so you can show your user what is on file and what your change would do — that save replaces the whole section, so a schedule you cannot see is a schedule you cannot safely replace. It also re params: client_id*, template_id*, period_id*, account_kind, limit, offset |
save_accounting_policies | Save the Significant Accounting Policies text (Note 2) your user has chosen, one policy per title. SEND THE COMPLETE SET EVERY TIME: this replaces all of Note 2, so any title you leave out of this call is removed — including one someone answered in the Datavrn app. Call list_statement_policy_choices first and send back every title. If your call would drop a saved policy, Datavrn saves nothing and params: client_id*, template_id*, period_id*, policies, removal_token, removal_count, on_behalf_of |
save_regulatory_affirmations | Save the CARO / Other Regulatory Information affirmations your user has confirmed, one per title. SEND THE COMPLETE SET EVERY TIME: this replaces the whole Other Regulatory Information note, so any title you leave out of this call is removed — including one someone answered in the Datavrn app. Call list_statement_policy_choices first and send back every title. If your call would drop a saved affir params: client_id*, template_id*, period_id*, affirmations, removal_token, removal_count, on_behalf_of |
list_statement_policy_choices | List every Significant Accounting Policy and Other Regulatory Information affirmation for this statement, with the text that will print, whether a template choice is still unresolved, and what was answered LAST YEAR. This is what makes two rules actionable rather than decorative: never resolve a bracketed choice for your user, and always tell them when an answer differs from last year. CHECK THE R params: client_id*, template_id*, period_id*, limit, offset |
get_finalise_readiness | Read the full finalisation state of one statement version, and get the approval finalise_statement needs. Call it ONCE immediately before finalising — it re-reads the stored workbook, so do not poll it. SHOW YOUR USER EVERY ROW THIS RETURNS — the gates that must be green, each warning they would be accepting and why, how many input cells are still empty, any control that could not be evaluated, an params: client_id*, snapshot_id*, on_behalf_of |
finalise_statement | Seal a statement version as Datavrn’s permanent client copy, recorded as authorised by the member you name. THIS IS NOT APPROVAL OR ADOPTION OF THE FINANCIAL STATEMENTS AND IT IS NOT A SIGNATURE. It does not discharge section 134(1) for a company or section 34(3) for an LLP. THERE IS NO UNDO. A change afterwards means generating a new version and finalising that one; the version you seal here stay params: client_id*, snapshot_id*, acknowledgments*, confirm_token*, on_behalf_of |
get_comparative_source_state | Check whether this statement’s previous-year comparative can be sealed, and get the approval assert_previous_year_no_activity needs. Datavrn refuses to finalise a statement whose previous-year figures come from a trial balance drawn AFTER the year-end closing entries: that derives a previous-year Profit and Loss of all zeroes which foots perfectly and is not last year’s results. When post_closing_ params: client_id*, template_id*, period_id*, on_behalf_of |
assert_previous_year_no_activity | Record your user’s assertion that the previous year genuinely had no activity, so this statement’s all-nil previous-year Profit and Loss is a fact rather than a closing-entry artefact. This clears Datavrn’s refusal to finalise it. THIS IS A PROFESSIONAL ASSERTION ABOUT A CLIENT’S ACCOUNTS, RECORDED IN THE NAMED MEMBER’S NAME AND KEPT WITH THE STATEMENT. Only send it when your user has told you, in params: client_id*, template_id*, period_id*, reason*, confirm_token*, on_behalf_of |
generate_schedule_iii | Queue the Schedule III workbook build (returns a job_id to poll with get_job — the build runs as a background job). REFUSES when ungrouped accounts exist unless acknowledged: before acknowledging, present the ungrouped accounts to your user and obtain their explicit go-ahead; record it in acknowledge_reason and pass the exact count in acknowledge_count — an acknowledgement WITHOUT its count is alw params: client_id*, template_id*, period_id*, acknowledge_unclassified, acknowledge_count, acknowledge_reason, acknowledge_multi_month_pnl, acknowledge_month_count |
get_job | Poll a background job by id until status is succeeded or failed. A failed job carries its user-safe error reason — show it to your user. Jobs run on a background worker that claims queued work on a schedule, so a job sitting at "queued" (0 attempts) for the first few minutes is NORMAL, not a fault — keep polling every ~30–60s and reassure the user it is being prepared; do NOT report this as an err params: job_id* |
list_snapshots | List the frozen Schedule III workbook versions for an entity (newest first), including each version’s period, template, and unclassified count at build time. params: client_id*, template_id |
get_workbook_download | Mint a short-lived signed URL for a frozen workbook version (the Excel file). Give the URL to your user to open in a browser — it needs no login and expires in about 10 minutes. The bytes are immutable and integrity-hashed. params: client_id*, snapshot_id* |
create_upload_link | Mint a single-use, login-free upload link so a file reaches Datavrn WITHOUT passing through your context, where it cannot truncate or corrupt. Use this whenever a human has the file (a trial balance export, etc.) — and also whenever YOU hold the file and it is larger than about 10 KB. This is the RELIABLE path at that size: inlined base64 mutates often enough that the damage arrives as a plausible params: client_id*, file_name*, format, source |
get_upload_link_status | Check an upload link's state: pending (the user has not uploaded yet), uploaded (returns the upload_id — continue with get_upload), or expired (mint a fresh link with create_upload_link). Poll after the user says they uploaded the file. params: link_id* |
get_statement_figures | Read a generated Schedule III statement's figures: the balance-sheet and profit-and-loss faces, current-year and previous-year balance-sheet tie verdicts separately (a null verdict means UNKNOWN, never a pass: either no comparative was captured, or the version predates per-column balance recording), the unclassified count, and the notes listed by number. Also returns bounded exception counts by ru params: client_id*, template_id*, period_id*, version |
get_statement_notes | Read the line-by-line breakdown of a generated statement's notes — every line's current and prior-year amount, and the note total. Pass note_numbers (from get_statement_figures' note_index) to fetch specific notes, or omit for all. Use this to answer "what's in Other Expenses?" or "what makes up trade receivables?". Each line has a kind: 'component' (an additive line), 'subtotal' (a presentational params: client_id*, template_id*, period_id*, version, note_numbers, lines_page |
get_tb_rows | Read the SOURCE DATA behind a statement: the trial-balance rows (account name, debit, credit) as landed for a period, BEFORE grouping — the pre-statement numbers, not statement figures. PREFER FILTERS over fetching everything: name_patterns (e.g. ['cash','bank','od']), side ('debit'/'credit' by net balance), and min_abs_balance return a small exact subset with its own debit/credit totals — e.g. wr params: client_id*, period_id*, name_patterns, side, min_abs_balance, page, page_size |
get_pending_work | Answer "what's left to do?" across every entity you can see — one row per entity, with what is blocking its Schedule III statement: whether the trial balance is in, how many accounts are still ungrouped, the latest generated version, and whether it has been finalised. Pass period_label to pick a period, or omit to default to the period most of your entities have a trial balance for (not necessaril params: period_label |
list_allocation_runs | MANAGEMENT data class. Discover persisted allocation runs and their separate cost-centre and profit-centre reconciliations; do not add them together. This does not generate or recompute allocation. Money is decimal-string rupees. Choose one allocation_dimension in a detail read. Results are ordered period, version, then run id, and the signed page_token is pinned to the complete filtered source: i params: client_id*, period, current_only, page_size, page_token |
get_allocation_account_figures | MANAGEMENT data class. Read one explicit cost or profit partition of the current persisted allocation run at account grain. Cost-centre and profit-centre reconciliations are independent views of the same P&L activity; do not add them. Books figure plus spreading adjustment equals MIS figure, all as decimal-string rupees. Filter account names or minimum absolute MIS amount before paging. The signed params: client_id*, period*, allocation_dimension*, account_name_patterns, min_abs_mis, page_size, page_token |
get_allocation_target_figures | MANAGEMENT data class. Read one explicit cost or profit partition of the current persisted allocation run at account × target × source × mode grain, with decimal-string allocated amounts. Cost-centre and profit-centre reconciliations are independent views of the same P&L activity; do not add them. Final post-step-down cost uses the complete selected cost population: non-step-down plus signed step- params: client_id*, period*, allocation_dimension*, account_name_patterns, target_types, allocation_sources, min_abs_amount, page_size, page_token |
get_spreading_reconciliation | MANAGEMENT data class. Read the persisted books-to-MIS spreading reconciliation, not a new allocation run. Accounts view gives account-grain books plus adjustments equals MIS; adjustments view requires one account and pages its rule adjustments. Money is decimal-string rupees. Whole-run summary figures never change with account filters. The signed page_token is source-pinned, so restart at page 1 params: client_id*, period*, view, account_id, account_name_patterns, page_size, page_token |
list_budgets | MANAGEMENT data class. Discover budget ids and versions without identity fields. Locked FX rate and all money-valued fields are decimal strings. Filter status or fiscal-year start before paging. The signed page_token is pinned to the complete filtered source; restart at page 1 if source_changed. This lists budget headers only, not cells, approvals identities, or a recalculated budget. params: client_id*, status, fiscal_year_start, page_size, page_token |
get_budget | MANAGEMENT data class. Read one versioned budget: identity-free header, its pinned P&L tree, and filtered/paginated cells with entered-versus-inferred truth. Amounts and locked FX rate are decimal strings. Filter months, lines, centres, or inference before paging; the signed page_token is source-pinned, so restart at page 1 if source_changed. Cells across different P&L lines are not one meaningful params: client_id*, budget_id*, month, line_codes, cost_centre_ids, inference, page_size, page_token |
get_variance_report | MANAGEMENT data class. Read the existing budget-or-prior variance report for a month; it never recalculates it. Amounts are decimal strings; a null actual or variance means unavailable, never zero. Rows view has whole-report unfiltered rollups and no cross-side grand total; filters affect only rows and filtered grain counts. Explanations view withholds internal notes and may redact structured PII. params: client_id*, period*, basis, view, line_codes, cost_centre_ids, page_size, page_token |
get_consolidated_statements | CONSOLIDATED data class. Read one sealed group profit-and-loss, balance-sheet, or cash-flow face for an exact periodicity and period. The response exposes presentation currency and exactly one decimal-string amount per line: section-natural for P&L/BS, signed cash movement for CFS. Amounts are persisted on the sealed run; P&L/BS labels are current display metadata and the signed page_token is sour params: group*, periodicity*, period*, statement, page_size, page_token |
list_cost_centres | List the cost centres for an entity. Use this before proposing account mappings so you can group the proposal by target name and distinguish operating from support centres. This is status-only: it returns names, short codes, kinds and each centre’s parent_cost_centre_id, never rupee amounts and never an owner’s name. Read parent_cost_centre_id (null at the top level) to show the user the hierarchy params: client_id*, page, page_size |
create_cost_centre | Create one cost centre for an entity after showing the user the exact name, kind, parent, effective date, and reason. This is one explicit centre at a time; there is no apply-all shortcut. After creating it, call list_cost_centres again and explain which mapping suggestions can now use it. params: client_id*, name*, centre_kind, parent_cost_centre_id, description, code, effective_from, reason* |
list_profit_centres | List the profit centres for an entity. Use this to explain available targets before a user confirms any explicit mapping. This is status-only: it returns names and hierarchy, never rupee amounts. params: client_id*, page, page_size |
create_profit_centre | Create one profit centre for an entity after showing the user the exact name, optional parent, and description. This is one explicit centre at a time; there is no apply-all shortcut. Re-list the centres after creation so the user can see the new target before any mapping confirmation. params: client_id*, name*, parent_profit_centre_id, description |
list_account_mappings | Review account-to-centre mapping status and deterministic suggestions for an entity. Each account carries TWO independent policies: mapping (the cost-centre policy) and profit_mapping (the profit-centre policy). Neither replaces the other. This is status-only: it returns account names, types, target names, confidence, reasons, and balance-bearing booleans, but never debit, credit, balance, or any params: client_id*, page, page_size, unmapped_only, profit_unmapped_only, balance_bearing_only, name_patterns |
confirm_centre_mappings | Persist only the explicit account-to-centre decisions the user approved. Before calling, show the proposal grouped by confidence tier and target with exact counts, call out every medium/low-confidence row, and get a clear approval for the enumerated items. Omitted accounts stay unchanged; there is no apply-all, auto-confirm, or use-suggestions flag. Each item writes ONE dimension, chosen by target params: client_id*, effective_from*, items*, removal_token, removal_count |
list_reporting_lines | Review reporting-line classification status and deterministic suggestions for an entity and reporting period. This is status-only: it returns names, line labels, confidence, reasons, and balance-bearing booleans, but never debit, credit, balance, or any rupee amount. Present suggestions grouped by confidence tier and target, with exact counts and both unmapped_total and unmapped_with_balance; do n params: client_id*, period_id*, page, page_size, unmapped_only, name_patterns |
confirm_reporting_lines | Persist only the explicit reporting-line decisions the user approved. Before calling, show the proposal grouped by confidence tier and target with exact counts, flag every medium/low-confidence row, and get clear approval for the enumerated decisions. Omitted accounts stay unchanged. Sending leaf_code:null permanently removes that account saved reporting line; send it only when the user explicitly params: client_id*, decisions*, removal_token, removal_count |
get_setup_status | Answer "how do I get started?", "what do I do next?", or help a user who seems lost setting up. Returns where they are in the journey from an empty organization to a finished Schedule III statement, and the ONE next step to take. Call it WITHOUT client_id first (the organization view): it lists the entities this credential can see, or — if there are none — the step to create the first one. Then ca params: client_id |
list_replacements | List what a connected data source’s AUTOMATIC syncs have REPLACED for one entity — each one showing what was overwritten, how many records, and whether it can still be undone. Call this when a user says figures for a past period look wrong or changed on their own, and after any surprise in a period a connector covers. Datavrn keeps the replaced data for 30 days from the moment it was replaced: wit params: client_id*, connection_id* |
preview_replacement_restore | Show EXACTLY what undoing one automatic sync would do, counted at this moment, and get the approval restore_replacement needs. destroy_count is how many records undoing it would DESTROY — everything currently held for that period, whoever or whatever put it there, including data a colleague uploaded since. restore_count is how many records would be put back. READ BOTH NUMBERS TO YOUR USER IN THEIR params: client_id*, connection_id*, event_id*, on_behalf_of |
restore_replacement | Undo one automatic sync: destroy what is currently held for that period and put back the records the sync replaced, recorded as authorised by the member you name. THIS DESTROYS DATA. Everything currently held in that period goes — including anything uploaded or synced since — and is replaced by what was there before. Datavrn keeps a record of what this destroys, but it is NOT offered back on this params: client_id*, connection_id*, event_id*, expected_destroy_count*, confirm_token*, on_behalf_of |
list_chart_rebaselines | List the uploads Datavrn is NOT counting as evidence of which entity a file belongs to. This happens when an entity’s chart of accounts grew or changed faster than Datavrn can vouch for from what it already holds — typically an acquisition, a migration, or a year-end restructure. NOTHING WAS REJECTED, BLOCKED OR CHANGED: the figures in those uploads are landed and live. What has not advanced is th params: client_id*, on_behalf_of |
preview_chart_rebaseline | Show ONE upload’s figures as they stand right now, and get the approval confirm_complete_chart needs. Call this after list_chart_rebaselines, for the one upload your user is considering. It reports the same counts the list does — how many distinctive ledger names Datavrn already treats as evidence (trusted_considered), how many this upload adds (incoming_considered), how many are on both sides (ma params: client_id*, source_snapshot_id*, on_behalf_of |
confirm_complete_chart | Record your user’s explicit confirmation that one upload is an entity’s COMPLETE CURRENT chart of accounts, so Datavrn starts treating it as evidence when checking whether future files belong to that entity. Recorded as authorised by the member you name. THIS IS A PROFESSIONAL JUDGMENT, NOT A CALCULATION. Datavrn will never make it from the numbers, and neither should you: call preview_chart_rebas params: client_id*, source_snapshot_id*, state_digest*, confirm_token*, on_behalf_of |
verify_connection | Confirm the Datavrn connection is working and report what it can do. Call this first — or whenever the user asks whether Datavrn is connected — to get back the organization, the access profile (what this connection may see and do), and the next step. Running it successfully also marks the connection healthy in the user’s Datavrn settings. params: none |
get_help | Get the Datavrn agent guide: how connecting works (OAuth and API key), what an assistant can do, how reading a statement as data works, and the guarantees and limits — plus the current list of tools. Call this to answer a user's questions about how Datavrn works from canonical documentation instead of guessing. params: none |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.