Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.datavrn/schedule-iii

REMOTE · APP.DATAVRN.COM

Deterministic Schedule III statements for Indian companies: trial balance in, Excel workbook out.

Available components

−1 this week 89 Trust /100

Last scanned (23 hours ago)

Scores higher than 96% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security94
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 22929 tokens (~322/item across 71 items; 71 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage89
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 67% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 71 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 17 Nov 26 −1
    • Tool “get_budget” rewrote its description, which is the text the model reads security
    • Tool “list_allocation_runs” rewrote its description, which is the text the model reads security
    • Tool “list_budgets” rewrote its description, which is the text the model reads security
    • Schema quality: 20692 → 22929 ▼ functional
    • New tool “get_entity_mis_catalogue” functional
    • New tool “get_entity_mis_numbers” functional
    • New tool “list_entity_mis_runs” functional
    • “ingest_upload” added an optional parameter “monthly_history_authority” cosmetic
    • “list_allocation_runs” dropped the optional parameter “current_only” cosmetic
    • “list_budgets” dropped the optional parameter “status” cosmetic
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 2 Nov 26 0
    • New tool “close_incomplete_mis_capture”, which the server declares destructive security
    • Tool “generate_schedule_iii” rewrote its description, which is the text the model reads security
    • “generate_schedule_iii” added an optional parameter “request_id” cosmetic
    • “ingest_upload” added an optional parameter “confirm_identity_correction” cosmetic
  • 10 Oct 26 0
    • Stability: fail → pass ▲ security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://app.datavrn.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=app.datavrn.com CN=YR2,O=Let's Encrypt,C=US 24 Oct 2026 22 Jan 2027 RSA 2048 SHA256-RSA 6f5fb9ef5832c467671c53c361adf9ed31f
SANs: app.datavrn.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of app.datavrn.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
datavrn.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://app.datavrn.com/.well-known/oauth-protected-resource/api/mcp"

Bearer resource_metadata="https://app.datavrn.com/.well-known/oauth-protected-resource/api/mcp"
Header Value
strict-transport-security max-age=15552000; includeSubDomains; preload
content-security-policy default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; form-action 'self' https://api.razorpay.com; img-src 'self' data: blob: https://jmkgxtzscatvuqefbiyq.supabase.co https://*.razorpay.com; font-src 'self' data:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline' https://*.razorpay.com; connect-src 'self' https://jmkgxtzscatvuqefbiyq.supabase.co wss://jmkgxtzscatvuqefbiyq.supabase.co https://o4511541413740544.ingest.de.sentry.io https://*.razorpay.com; frame-src 'self' https://api.razorpay.com https://checkout.razorpay.com; worker-src 'self' blob:; manifest-src 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(), usb=(), browsing-topics=()

Protected resource metadata

Document https://app.datavrn.com/.well-known/oauth-protected-resource/api/mcp
Retrieved Yes
Resource https://app.datavrn.com/api/mcp
Authorisation server https://jmkgxtzscatvuqefbiyq.supabase.co/auth/v1

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://app.datavrn.com/api/mcp Verified 200
http (plaintext) http://app.datavrn.com/api/mcp HTTPS enforced 308 https://app.datavrn.com/api/mcp
MCP tools · 71 exposed · ~22,929 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
assert_previous_year_no_activity ~468

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 their own words, that the previous year had no activity — a dormant entity is the case it is for. NEVER write the reason yourself and never paraphrase it into something firmer: send what they said. If they are unsure, or if the previous year DID trade and the trial balance was simply taken after closing, do not call this — the other two remedies in get_comparative_source_state are the correct ones. Call get_comparative_source_state first, read out the finding, get their explicit go-ahead, and send the confirm_token it returned. Datavrn refuses if the previous-year figures changed after you read the state, and nothing is recorded. It can be withdrawn in Datavrn if it was recorded in error; withdrawing restores the refusal.

NameTypeReqDescription
client_idstringyesThe entity (client) id — from list_clients.
confirm_tokenstringyesThe approval from get_comparative_source_state. Call it first and present its finding to your user.
on_behalf_ofstring–The email address your user signs in to Datavrn with. This records who authorised the change alongside the connection that made it. REQUIRED on an API-key connection — ask your user for it, do not gu…
period_idstringyesThe reporting period id — from list_periods.
reasonstringyesYour user’s own words: why the previous year had no activity. Recorded with the statement and shown to whoever reviews it.
template_idstringyesThe statement template id (e.g. 'schedule3_v1' Division I; see list_snapshots/workspace).

No output schema declared.

No examples provided.

close_incomplete_mis_capture ~257

Close one incomplete MIS generation only after your user explicitly chooses to close that run. This permanently marks an eligible incomplete generation as failed while preserving its history. The original failure cause remains unknown. Use the same original initiating account and exact original delegated credential, with current Generate and entity access. The server refuses if capture committed, the run is busy, authority changed, or a safe closeout cannot be proved. A successful response contains only the run status and committed closeout receipt. If the outcome is unconfirmed, refresh and verify this same run before generating again. Only after confirmed closeout may the user separately choose ordinary Generate; this tool never starts another generation. Recorded as authorised by the member resolved for this connection.

NameTypeReqDescription
on_behalf_ofstring–The email address your user signs in to Datavrn with. This records who authorised the change alongside the connection that made it. REQUIRED on an API-key connection — ask your user for it, do not gu…
run_idstringyesThe exact incomplete MIS run id the user chose to close.

No output schema declared.

No examples provided.

confirm_capture_review ~420

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-ahead. Never confirm a review that has not happened. Saving figures or text does NOT complete these two sections and never has; only this confirmation does. The confirmation is pinned to the exact set that was reviewed, so ANY later save to that section withdraws it — if a confirmation appears not to stick, the next step is to re-review and confirm again, never to retry. Confirming again after such a change supersedes the earlier confirmation: it is marked withdrawn (it stays on the record) and the response names what was withdrawn. Re-confirming also invalidates any finalise approval you already hold. Only two sections take a review confirmation: the previous-year comparative and the disclosure set. Every other section is answered by saving its rows, or by declare_capture_na. Datavrn notifies the member you name that this was recorded in their name. Generate a fresh version after your last capture change — finalisation checks the version’s frozen capture state, not today’s.

NameTypeReqDescription
capture_kindstringyes–
client_idstringyesThe entity (client) id — from list_clients.
notestring––
on_behalf_ofstring–The email address your user signs in to Datavrn with. This records who authorised the change alongside the connection that made it. REQUIRED on an API-key connection — ask your user for it, do not gu…
period_idstringyes–
reason_codestringyes–
template_idstringyes–

No output schema declared.

No examples provided.

confirm_centre_mappings ~494

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_type: "cost_centre" writes the cost-centre policy and "profit_centre" writes the profit-centre policy. The two are independent — writing one never replaces the other — and the same account may appear once per dimension in a single call. A centre policy can only be set on a profit-and-loss account: an account Datavrn resolves to a balance-sheet type, or has not classified yet, is refused by name and nothing is saved. After the write, report confirmed, unmapped_total and unmapped_with_balance (the cost dimension), and profit_unmapped_total and profit_unmapped_with_balance (the profit dimension) so the user knows exactly what remains. When profit_centres_total is 0 the profit dimension is not in use and no account needs a profit-centre policy — never report the entity as profit-mapped. Read profit_mapped_total beside it: 0 means no account holds one, and above 0 means the dimension has been closed while that many accounts still carry a saved policy pointing at a deactivated centre. The counts describe the policies in force on counts_as_of. A write can be saved and still not be in force, in two ways, and next_action says which: effective_from later than counts_as_of (not in force yet), or superseded_total above 0 (that many of these accounts already carry a LATER version that is in force, so this back-dated write changes nothing visible). In either case do not repeat the call. This tool never returns rupee amounts.

NameTypeReqDescription
client_idstringyesThe entity (client) id — from list_clients.
effective_fromstringyesThe effective date shown to the user.
itemsarrayyesEvery account decision explicitly approved by the user; never a blanket flag.
removal_countinteger–The exact removal count returned by the removal preview.
removal_tokenstring–Only include the short-lived token returned by the removal preview for this exact proposal.

No output schema declared.

No examples provided.

confirm_column_mapping ~102

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.

NameTypeReqDescription
mappingobjectyes–
optionsobject––
save_asstring––
upload_idstringyesThe upload session id returned by upload_trial_balance.

No output schema declared.

No examples provided.

confirm_complete_chart ~437

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_rebaseline for that upload first, read its counts to your user, and ask them plainly whether that upload is the entity’s whole book now. Confirming a file that is NOT the entity’s chart teaches Datavrn the wrong chart and weakens wrong-entity detection for that entity from then on. Send back the state_digest and confirm_token from the SAME preview_chart_rebaseline response, unchanged. Datavrn refuses and changes nothing if: the entity’s uploads moved after you were shown those figures, someone already confirmed this upload, the upload no longer needs confirming, or it is one Datavrn asked about directly — for those, answering that question is what settles it. Nothing about the landed figures changes: this affects only which uploads count as evidence of identity.

NameTypeReqDescription
client_idstringyesThe entity (client) id — from list_clients.
confirm_tokenstringyesThe approval from preview_chart_rebaseline. Call it first and present its counts to your user.
on_behalf_ofstring–The email address your user signs in to Datavrn with. This records who authorised the change alongside the connection that made it. REQUIRED on an API-key connection — ask your user for it, do not gu…
source_snapshot_idstringyesThe upload’s id — the `snapshot_id` field of a list_chart_rebaselines row.
state_digeststringyesThe state_digest from the same preview_chart_rebaseline response, unchanged. It pins the figures your user was shown; a different one is refused.

No output schema declared.

No examples provided.

confirm_groupings ~165

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-unclassified account is an idempotent no-op. Every row must be explicit — there is deliberately no "apply all suggestions" option.

NameTypeReqDescription
client_idstringyesThe entity (client) id — from list_clients.
decisionsarrayyes–
grouping_versioninteger––
removal_countinteger––
removal_tokenstring––
template_idstringyes–

No output schema declared.

No examples provided.

confirm_reporting_lines ~189

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 asked to clear that row. There is no apply-all or auto-confirm flag. The response tells you how many were confirmed, cleared, and whether the balance-bearing set is fully mapped; never claim completion without checking those fields.

NameTypeReqDescription
client_idstringyesThe entity (client) id — from list_clients.
decisionsarrayyes–
removal_countinteger–The exact removal count returned by the removal preview.
removal_tokenstring–Only include the short-lived token returned by the removal preview for this exact proposal.

No output schema declared.

No examples provided.

copy_capture_declarations ~245

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. Answers already recorded for this period are left alone. Generate a fresh version after your last capture change — finalisation checks the version’s frozen capture state, not today’s.

NameTypeReqDescription
client_idstringyesThe entity (client) id — from list_clients.
on_behalf_ofstring–The email address your user signs in to Datavrn with. This records who authorised the change alongside the connection that made it. REQUIRED on an API-key connection — ask your user for it, do not gu…
period_idstringyes–
template_idstringyes–

No output schema declared.

No examples provided.

create_client ~62

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.

NameTypeReqDescription
business_model_code–––
namestringyes–

No output schema declared.

No examples provided.

create_cost_centre ~190

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.

NameTypeReqDescription
centre_kindstring–Operating or shared-support centre; defaults to operating.
client_idstringyesThe entity (client) id — from list_clients.
code––Optional short code.
description––Optional plain-language description.
effective_fromstring–Date from which this centre applies; defaults to the start of the entity data.
namestringyesThe cost-centre name to create.
parent_cost_centre_id––Optional existing parent cost-centre id.
reasonstringyesWhy the user asked for this centre.

No output schema declared.

No examples provided.

create_profit_centre ~123

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.

NameTypeReqDescription
client_idstringyesThe entity (client) id — from list_clients.
description––Optional plain-language description.
namestringyesThe profit-centre name to create.
parent_profit_centre_id––Optional existing parent profit-centre id.

No output schema declared.

No examples provided.

create_upload_link ~340

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-looking trial balance rather than an obvious error, while the link delivers the bytes byte-perfect. Two ways to deliver the file: a HUMAN opens upload_url in their browser and chooses the file; a PROGRAMMATIC caller that already holds the file on disk POSTs it to the SEPARATE upload_post_url as a multipart form with a single `file` field (upload_url is the human page and will not accept a POST). The POST reply carries received_file_hash — compare it to your local sha256 before confirming the mapping. The link stages the file for ONE entity and expires in about 15 minutes; nothing is ingested until the column mapping is confirmed.

NameTypeReqDescription
client_idstringyesThe entity (client) id — from list_clients.
file_namestringyesThe file the user is expected to upload, e.g. 'tb-2026-03.xlsx' (shown on the upload page).
formatstring–Leave unset — the assistant handles Trial Balances only; any other format is refused (use the Datavrn web app).
sourcestring–Set 'tally_file' when the file is a Tally xlsx export; omit otherwise.

No output schema declared.

No examples provided.

declare_capture_na ~528

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 assertion, recorded as authorised by them — ask which one is true, and never guess. NOT every reason is available for every section — call get_schedule3_workspace and read allowed_reason_codes on the section before you ask your user, so you never put a choice to them that Datavrn will refuse. The restrictions: Settings takes NO answer here at all (it is only answered by saving the settings); share capital and partner capital take only "nothing this period", because those sections are shown only for statement formats they apply to, so "does not apply" can never be true; and "first year" belongs only to previous-year figures. To record a REVIEW being complete (previous-year figures, disclosures) use confirm_capture_review instead; this tool cannot make that assertion. A section can only hold one active answer. If the section’s current answer is still standing, this call refuses — revoke it with revoke_capture_declaration first. If the current answer was already WITHDRAWN by later changes (Datavrn shows the section as unanswered), this call supersedes it: the old answer is marked withdrawn and stays on the record, and the response names what was withdrawn. An answer is never edited in place. Superseding or changing an answer invalidates any finalise approval you already hold — the next finalise_statement will ask you to review the current state again. Generate a fresh version after your last capture change — finalisation checks the version’s frozen capture state, not today’s.

NameTypeReqDescription
capture_kindstringyes–
client_idstringyesThe entity (client) id — from list_clients.
notestring––
on_behalf_ofstring–The email address your user signs in to Datavrn with. This records who authorised the change alongside the connection that made it. REQUIRED on an API-key connection — ask your user for it, do not gu…
period_idstringyes–
reason_codestringyes–
template_idstringyes–

No output schema declared.

No examples provided.

finalise_statement ~418

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 stays sealed. Call get_finalise_readiness first, show your user every gate and every warning it returns, get their explicit go-ahead, and only then send the confirm_token it gave you together with the acknowledgements. Never acknowledge a warning your user has not seen, and never write the acceptance reason yourself — it is their professional judgment in their own words. Datavrn will refuse if anything about the statement changed after you read the state, and nothing will be finalised. If the response comes back with reused set to true, a finalisation of this same version was already under way: nothing new was done and your approval was not used. Do not call finalise_statement again — the status field says where that finalisation is (queued, running, or paused, which means it hit a temporary problem and Datavrn will retry it on its own). Poll get_job with the job_id and tell your user what it says.

NameTypeReqDescription
acknowledgmentsobjectyes–
client_idstringyesThe entity (client) id — from list_clients.
confirm_tokenstringyes–
on_behalf_ofstring–The email address your user signs in to Datavrn with. This records who authorised the change alongside the connection that made it. REQUIRED on an API-key connection — ask your user for it, do not gu…
snapshot_idstringyes–

No output schema declared.

No examples provided.

generate_schedule_iii ~349

Queue the Schedule III workbook build (returns a job_id to poll with get_job — the build runs as a background job). Supply a fresh request_id UUID for a new request; retain that UUID and unchanged arguments when retrying after an uncertain response. Changing an acknowledgment or other argument requires a new UUID. 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 always re-demanded. For a multi-month P&L window, acknowledge_multi_month_pnl is required only when the refusal reports period-activity or basis-not-captured inputs; show your user the exact reported risky-month count and confirm only the P&L figures for that subset. Declared cumulative inputs have already been normalized and must not be described as period movements. If the refusal reports invalid cumulative normalization, do not acknowledge it away: correct and re-upload the affected input. Never acknowledge anything the user has not seen. Once queued, the build usually completes in a few minutes — tell your user their statements are being prepared and poll get_job periodically; do not present the wait as a problem.

NameTypeReqDescription
acknowledge_countinteger––
acknowledge_month_countinteger––
acknowledge_multi_month_pnlboolean––
acknowledge_reasonstring––
acknowledge_unclassifiedboolean––
client_idstringyesThe entity (client) id — from list_clients.
period_idstringyes–
request_idstring––
template_idstringyes–

No output schema declared.

No examples provided.

get_allocation_account_figures ~280

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 page_token is source-pinned, so restart at page 1 if source_changed. known_stale and not_assessed disclose run state; neither means fresh.

NameTypeReqDescription
account_name_patternsarray–Up to 10 case-insensitive account-name substrings; any match is retained.
allocation_dimensionstringyesRequired partition: cost for cost-centre or step-down questions; profit for profit-centre questions. Do not add the two views.
client_idstringyesThe entity (client) id — from list_clients.
min_abs_misstring–Minimum absolute MIS figure in rupees as a decimal string, e.g. '100000'.
page_sizeinteger–Rows per source-pinned page (default 50, max 200).
page_tokenstring–Signed continuation from the prior page; restart without it if source_changed.
periodstringyesManagement month in YYYY-MM.

No output schema declared.

No examples provided.

get_allocation_target_figures ~439

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-down. Filter allocation_sources=['step_down'] only to inspect transfers and confirm their run net is zero. Accounted equals assigned plus Unallocated; Unallocated is not additional. For profit centres, choose profit. Use filters before paging; the signed page_token is source-pinned, so restart at page 1 if source_changed. Target labels use the current governed centre timeline evaluated at the run period (target_labels_frozen: false); persisted allocation amounts stay unchanged. A controlled in-period centre correction changes a displayed label and invalidates the page token; restart at page 1 without regenerating allocation. Review run staleness and methodology, and regenerate when either changed. An integrity failure means regenerate, retry, then contact support if it recurs. No owners, descriptions, source transactions, or recomputation are returned.

NameTypeReqDescription
account_name_patternsarray–Up to 10 case-insensitive account-name substrings; any match is retained.
allocation_dimensionstringyesRequired partition: cost for cost-centre or step-down questions; profit for profit-centre questions. Do not add the two views.
allocation_sourcesarray–Restrict to allocation sources.
client_idstringyesThe entity (client) id — from list_clients.
min_abs_amountstring–Minimum absolute allocated amount in rupees as a decimal string, e.g. '100000'.
page_sizeinteger–Rows per source-pinned page (default 50, max 200).
page_tokenstring–Signed continuation from the prior page; restart without it if source_changed.
periodstringyesManagement month in YYYY-MM.
target_typesarray–Restrict to allocation target types.

No output schema declared.

No examples provided.

get_budget ~332

MANAGEMENT data class. Read the exact existing ACTIVE budget_id returned by list_budgets for the requested Entity and fiscal year, including earlier fiscal years: identity-free header, its pinned P&L tree, and filtered/paginated cells with entered-versus-inferred truth. A draft or archived id is not readable and is never replaced inside a read. Amounts and locked FX rate are decimal strings. Filter months, lines, centres, or inference before paging. The signed page_token binds this exact id and source; if source_changed after a replacement, discard partial results, rediscover ACTIVE with list_budgets and start the new exact id at page 1 without the old token. Never combine budget versions or select a substitute mid-walk. Cells across different P&L lines are not one meaningful grand total, so no cross-line grand total is exposed. No people, ownership, editability, or approval identities are returned.

NameTypeReqDescription
budget_idstringyesBudget id from list_budgets.
client_idstringyesThe entity (client) id — from list_clients.
cost_centre_idsarray–Up to 25 cost-centre ids.
inferencestring–Cell inference state (default all).
line_codesarray–Up to 25 P&L line codes.
monthstring–Optional budget month in YYYY-MM.
page_sizeinteger–Cells per source-pinned page (default 100, max 200).
page_tokenstring–Signed continuation from the prior page; restart without it if source_changed.

No output schema declared.

No examples provided.

get_comparative_source_state ~422

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_detected is true, READ THE WHOLE finding TO YOUR USER — what the state is and all three ways out — and let them choose. Never choose for them. Two of the three remedies are things only they can do (upload the pre-closing trial balance, or enter last year’s signed figures as previous-year values, then generate a fresh version). The third is an assertion that the previous year genuinely had NO ACTIVITY, which is a statement about their client’s accounts, in their words, recorded in their name — a dormant company is the case it exists for. The approval is single-use, expires in 15 minutes, and is tied to this statement, this connection and the member you name; if the previous-year figures change in between, the assertion will be refused and you start again from here. If nothing is wrong there is no approval to hand back, because there is nothing to assert.

NameTypeReqDescription
client_idstringyesThe entity (client) id — from list_clients.
on_behalf_ofstring–The email address your user signs in to Datavrn with. This records who authorised the change alongside the connection that made it. REQUIRED on an API-key connection — ask your user for it, do not gu…
period_idstringyesThe reporting period id — from list_periods.
template_idstringyesThe statement template id (e.g. 'schedule3_v1' Division I; see list_snapshots/workspace).

No output schema declared.

No examples provided.

get_consolidated_statements ~859

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 source-fingerprinted across the complete safe face, so a changed value or label requires restarting at page 1. A stale sealed run is disclosed on every page and is never called current. Member names, components, eliminations, journal references and lineage are not returned. QUALIFICATIONS. A response may carry `owned_share_capital_caveat` (at seal, share capital owned by the group could not be eliminated, so those amounts remained inside consolidated share capital as the engine computed it; the DISPLAYED line may differ in either direction where a manual journal also moved it, so never characterise the direction from this field alone) and always carries `domestic_cash_flow_caveat`. These qualify specific statement lines. When a caveat is present, any figure it qualifies MUST be presented together with its qualification — never the number alone. `owned_share_capital_caveat` is null when the run was read and carries no such qualification, and `{status: "unavailable"}` when the run’s qualification record could not be read at all, which is not the same as clean: say so rather than presenting the figures as final. WITHHELD CASH FLOW. `cash_flow_status` may say the cash flow was not presented — for a group with a foreign member, or for a window with no opening balance sheet to measure from. An empty `cash_flow` then means the statement was WITHHELD, never that the group had no cash movements: say so. For the missing-opening-basis case `cash_flow_refusal` carries the cause, the message and `remedies`, each tagged with the channel that can perform it — `agent_or_app` you can do here,…

NameTypeReqDescription
groupstringyesAn active group UUID or its exact case-insensitive display name.
page_sizeinteger–Rows per source-pinned page (default 50, max 100).
page_tokenstring–Signed continuation from the prior page; restart without it if source_changed.
periodstringyesThe period matching periodicity.
periodicitystringyesPeriod grammar: monthly YYYY-MM, quarterly FYyyyy-Qn, annual FYyyyy.
statementstring–Statement face (default pnl).

No output schema declared.

No examples provided.

get_entity_mis_catalogue ~466

Inspect canonical current Entity MIS numerical coverage for the run_id returned by current-run discovery for the requested reporting period. Superseded versions are not accessible. The returned version is a source citation, not a selector. If source_changed is returned, rediscover the current run and restart at page 1. Reviewed codecs cover ordinary Entity financial statement populations returned by this catalogue, cumulative_variance_tracking year-to-date profit after tax and services_lockup detail populations contract_lockup_v5 and customer_lockup_v5 plus its services_lockup visual population and the additional reviewed native V5 detail and visual populations returned by this catalogue. The catalogue also admits four reviewed legacy business detail populations: inventory_aging/v4_aging_bucket, cohort_retention/v3_cohort_cell, churn_reasons/v3_churn_reason and at_risk_customers/v5_at_risk_raw_summary; recovery/editor and opaque-reference workflows are excluded. The current catalogue additionally admits shared statement candidates across twelve report families, including Services, Schools and statutory summaries, conditional on actual current saved availability. Statutory facts identify authenticated saved-row occurrences, not V2 identities or distinct economic totals; never deduplicate or aggregate equal-looking rows. Excluded rows without typed amounts/counts retain state and a context gap, never values parsed from prose. Native comparisons within a current report are current output. Native headlines and period_highlights are scalar candidates with key equal to report_id; saved claims and five Headlines counts are qualified on read, not reconstructed from their source reports. Scalar admission does not establish saved body availability or whole-MIS coverage. Typed and visual catalogue entries require body qualification on each read: materialized:null and sourceState:pending_qualification mean materialization is unknown, not absent or already qualified. Other nati…

NameTypeReqDescription
client_idstringyesThe entity (client) id — from list_clients.
run_idstringyesCurrent Entity run UUID returned by list_entity_mis_runs; never a Group id.

No output schema declared.

No examples provided.

get_entity_mis_numbers ~1,439

Read native current Entity MIS numbers, states, units, periods and source references without recomputation, for any requested reporting period including earlier periods. Available sealed output does not require approval; disclose its actual approval status. Currently serves ordinary Entity financial statement populations returned by the catalogue, cumulative_variance_tracking year-to-date profit after tax and the reviewed services_lockup detail populations contract_lockup_v5 and customer_lockup_v5 plus visual population services_lockup and the additional reviewed native V5 detail and visual populations in the current catalogue. Also reads the four reviewed legacy business detail populations inventory_aging/v4_aging_bucket, cohort_retention/v3_cohort_cell, churn_reasons/v3_churn_reason and at_risk_customers/v5_at_risk_raw_summary. These facts retain period:null/not_declared; dates and months are context only. Cohort ratios remain fractions, native and presentation money retain their distinct currencies, and fx_rate_per_1e4 is an unchanged scaled integer, never a second conversion. Repeated aging population operands are non-additive across buckets. At-risk rules and evidence are saved source results, never rescore them. Preserve unavailable or incomplete qualification and withheld names/source text; only positively qualified fixed labels pass. Shared statement candidates in the current catalogue additionally preserve native operational and employee_pay_deferred figures, Schools saved wrappers and statutory per-row currencies. Availability and body/context qualification remain conditional; no whole-MIS promise. Statutory facts identify authenticated saved-row occurrences, not V2 identities or distinct economic totals; never deduplicate or aggregate equal-looking rows. Excluded rows without typed amounts/counts retain state and a context gap, never values parsed from prose. Native comparison columns inside the current report are current output. Use native periods when…

NameTypeReqDescription
client_idstringyesThe entity (client) id — from list_clients.
page_sizeinteger––
page_tokenstring–Signed immutable-source continuation from the previous page.
population_keystring–Exact named population key from the catalogue; defaults to report_id for statement reads.
population_kindstring–Named population kind from the catalogue; defaults to statement.
report_idstringyesExact report identifier returned by the catalogue.
run_idstringyesCurrent Entity run UUID returned by list_entity_mis_runs.

No output schema declared.

No examples provided.

get_finalise_readiness ~403

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, and capture_live_diverged_message when it is present — before you finalise. Do not summarise the warnings away. capture_live_diverged_message means a capture answer changed after this version was generated: the version can still be sealed as it stands, and generating a fresh one is the alternative. Read it out and let your user choose. A control that "could not be evaluated" is not a pass: it is a check Datavrn did not run, and your user is entitled to know what was not checked before they seal the version. The approval is single-use, expires in 15 minutes, and is tied to this exact version, this connection and the member you name — if anything about the statement changes in between, finalise_statement will refuse and you start again from here. If your connection is not permitted to finalise, you still get the whole state; there is simply no approval to hand back.

NameTypeReqDescription
client_idstringyesThe entity (client) id — from list_clients.
on_behalf_ofstring–The email address your user signs in to Datavrn with. This records who authorised the change alongside the connection that made it. REQUIRED on an API-key connection — ask your user for it, do not gu…
snapshot_idstringyesThe statement version id — from list_snapshots or get_schedule3_workspace.

No output schema declared.

No examples provided.

get_help ~72

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_job ~148

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 error or a Datavrn bug. Only if it is still "queued" well past a few minutes should you tell the user it is taking longer than usual.

NameTypeReqDescription
job_idstringyesThe job id returned by generate_schedule_iii.

No output schema declared.

No examples provided.

get_partner_capital ~263

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 returns the total of the capital-account profit-sharing ratios, because Datavrn warns about a total that is not 100% only when at least two rows carry a ratio.

NameTypeReqDescription
account_kindstring–Limit to one section: 'capital' is Note 3a, 'current' is Note 3b. Omit for both.
client_idstringyesThe entity (client) id — from list_clients.
limitinteger–Page size (default 50, max 200).
offsetinteger–Rows to skip (default 0).
period_idstringyesThe reporting period id — from list_periods.
template_idstringyesThe statement template id (e.g. 'schedule3_v1' Division I; see list_snapshots/workspace).

No output schema declared.

No examples provided.

get_pending_work ~279

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 necessarily the newest — one entity uploading a future period early will not flip the board). Rows include deep links that open the Datavrn web app (a login is needed there). It also answers a second question nothing else here does: restorable_replacements lists automatic connector syncs that REPLACED an entity's data and can still be undone, soonest-closing first, each with the date its 30-day undo window shuts — after that the replaced data cannot be put back, and no message ever announces that clock running out, so raise these with your user rather than waiting to be asked (use list_replacements and preview_replacement_restore on the ids given; restorable_replacements_omitted says how many more were not listed).

NameTypeReqDescription
period_labelstring–Reporting period label, e.g. '2026-03'; omit to default to the period most of your entities have a trial balance for.

No output schema declared.

No examples provided.

get_schedule3_workspace ~138

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.

NameTypeReqDescription
client_idstringyesThe entity (client) id — from list_clients.
period_idstringyesThe reporting period id — from list_periods.
template_idstringyesThe statement template id (e.g. 'schedule3_v1' Division I; see list_snapshots/workspace).

No output schema declared.

No examples provided.

get_setup_status ~297

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 call it again WITH one entity’s client_id for that entity’s full step-by-step path (upload trial balance → confirm groupings → capture figures → generate → download). Each step has a status (done / next / todo / blocked / web_only) and either the exact tool to call or a web-app link. NARRATE ONE STEP AT A TIME — walk the user through the single `next` step; do not dump the whole list unprompted. Steps marked web_only are done in the Datavrn web app and need a login — never claim you can do them yourself. This tool reports STATUS only (counts, names, what is done) — it never returns a figure or balance; read those with get_statement_figures once a statement is generated.

NameTypeReqDescription
client_idstring–An entity id (from list_clients or the organization view) for that entity’s full path; omit for the organization-level overview and, on an empty org, the create-entity step.

No output schema declared.

No examples provided.

get_spreading_reconciliation ~255

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 if source_changed. Raw warning context is withheld; known_stale and not_assessed are disclosure states, not freshness claims.

NameTypeReqDescription
account_idstring–Required for adjustments view; an account in this entity and run.
account_name_patternsarray–Up to 10 case-insensitive account-name substrings; any match is retained.
client_idstringyesThe entity (client) id — from list_clients.
page_sizeinteger–Rows per source-pinned page: accounts default 25/max 100; adjustments default 50/max 200.
page_tokenstring–Signed continuation from the prior page; restart without it if source_changed.
periodstringyesManagement month in YYYY-MM.
viewstring–accounts (default) or adjustments; adjustments requires account_id.

No output schema declared.

No examples provided.

get_statement_figures ~367

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 rule/severity and the frozen control changes versus the immediately previous recorded version; it never recomputes either from live books. Figures come from a generated version (the latest unless you pass a specific version) and match the workbook exactly. If the version was generated before figure reads existed it returns available:false with reason "figures_not_available" and only the legacy flat tie verdict; tell the user to generate the statement again, read the latest version, then retry. For a note's line-by-line breakdown, use its note_index entry with get_statement_notes. Amounts are decimal strings in rupees. ONE EXCEPTION: the profit-and-loss face ends with the statutory earnings-per-share rows, marked kind:"eps". Their figures are ₹ PER SHARE, not rupees of profit — report them as EPS and never add them into a face total. They are null until the weighted average share counts are saved in statement settings. Figures are Datavrn's deterministic engine output; interpretation is your assistant's.

NameTypeReqDescription
client_idstringyesThe entity (client) id — from list_clients.
period_idstringyesThe reporting period id — from list_periods.
template_idstringyesThe statement template id (e.g. 'schedule3_v1' Division I; see list_snapshots/workspace).
versioninteger–A specific statement version; omit for the latest.

No output schema declared.

No examples provided.

get_statement_notes ~419

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 group subtotal — do NOT add it into the total, or you double-count), or 'header'. Fixed-asset / intangible notes carry a `block` per class with gross_block, accumulated depreciation, and net (the additions/deletions movement schedule itself lives in the workbook). If the full set is too large it returns too_large:true with a note_index — fetch note_numbers in small batches. A single very large note (e.g. a PPE schedule or an ageing note) is returned in explicitly-flagged line pages: each page carries the authoritative note total, lines_page, lines_total, and has_more_lines — keep fetching lines_page until has_more_lines is false; never treat one page's lines as the whole note. Amounts are decimal strings in rupees. Figures are Datavrn's deterministic engine output; interpretation is your assistant's.

NameTypeReqDescription
client_idstringyesThe entity (client) id — from list_clients.
lines_pageinteger–For a single very large note returned in line pages: the 1-based line page to fetch (fetch exactly one note; keep going until has_more_lines is false).
note_numbersarray–Specific note numbers to fetch (from note_index); omit for all notes.
period_idstringyesThe reporting period id — from list_periods.
template_idstringyesThe statement template id (e.g. 'schedule3_v1' Division I; see list_snapshots/workspace).
versioninteger–A specific statement version; omit for the latest.

No output schema declared.

No examples provided.

get_tb_rows ~395

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. wrong-side cash accounts = name_patterns ['cash','bank'] + side 'credit'. Paginated (page 1-based; page_size default 50, max 500). These are the CURRENT live rows: statement figures are frozen at a generated version, so if the trial balance was re-uploaded after a version was generated, these rows may not tie to that version (the response `note` says so). Amounts are decimal strings in rupees. Figures are Datavrn's deterministic engine output; interpretation is your assistant's.

NameTypeReqDescription
client_idstringyesThe entity (client) id — from list_clients.
min_abs_balancestring–Keep only accounts whose balance (the larger of its debit/credit) is at least this many rupees — a decimal string like '100000'.
name_patternsarray–Up to 10 case-insensitive substrings; an account matches if its name contains ANY of them (e.g. ['gst','tds']).
pageinteger–1-based page number (default 1).
page_sizeinteger–Rows per page (default 50, max 500 — prefer filters over big pages).
period_idstringyesThe reporting period id — from list_periods.
sidestring–Keep only accounts whose net balance falls on this side (debit = debits exceed credits). Accounts netting to zero match neither.

No output schema declared.

No examples provided.

get_upload ~61

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.

NameTypeReqDescription
upload_idstringyesThe upload session id returned by upload_trial_balance.

No output schema declared.

No examples provided.

get_upload_link_status ~76

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.

NameTypeReqDescription
link_idstringyesThe link id returned by create_upload_link.

No output schema declared.

No examples provided.

get_variance_report ~252

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. Filter lines or centres before paging; the signed page_token is source-pinned, so restart at page 1 if source_changed.

NameTypeReqDescription
basisstring–Comparator basis (default budget).
client_idstringyesThe entity (client) id — from list_clients.
cost_centre_idsarray–Up to 25 cost-centre ids.
line_codesarray–Up to 25 P&L line codes.
page_sizeinteger–Rows per source-pinned page (default 50, max 100).
page_tokenstring–Signed continuation from the prior page; restart without it if source_changed.
periodstringyesManagement month in YYYY-MM.
viewstring–Report rows (default) or safe explanations.

No output schema declared.

No examples provided.

get_workbook_download ~92

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.

NameTypeReqDescription
client_idstringyesThe entity (client) id — from list_clients.
snapshot_idstringyesThe snapshot id from list_snapshots.

No output schema declared.

No examples provided.

ingest_upload ~322

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 the SAME call adding removal_token and removal_count exactly as returned. acknowledge_warnings is IGNORED on this connection — the token is the only acknowledgment, so sending it changes nothing. A clean, additive ingest needs no token and succeeds on the first call. Returns the ingestion outcome including any notices.

NameTypeReqDescription
acknowledge_warningsboolean––
acknowledged_state_digeststring–Browser/REST only, and IGNORED on the agent connection exactly as acknowledge_warnings is: the destroy_state_digest returned by the confirm-mapping step, resent unchanged so the server can prove the…
confirm_identity_correctionboolean––
confirm_mergesarray––
monthly_history_authorityobject––
removal_countinteger–The exact removal count returned by the removal preview.
removal_tokenstring–Only include the short-lived token returned by the removal preview for this exact upload.
upload_idstringyesThe upload session id returned by upload_trial_balance.

No output schema declared.

No examples provided.

list_account_mappings ~615

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 rupee amount. Always present the rows grouped by confidence tier and target, state exact counts, flag every medium/low-confidence row, and show the completion counts: unmapped_total and unmapped_with_balance are the COST dimension (summary.scope says so), and profit_unmapped_total and profit_unmapped_with_balance are the profit dimension. Never add the two dimensions together, and never call an entity fully mapped on the cost counts alone. Do not call any count pending. Suggestions exist for the cost dimension only: suggestion_groups never describes profit work, and each row’s centre_suggestion carries dimension "cost" — never present it as an answer to a profit-centre question. A row carrying mapping_targets_inactive is confirmed onto a cost centre that has since been DEACTIVATED, and a row carrying profit_mapping_targets_inactive is the same fact on the profit dimension: those target ids are absent from the centres and profit_centres lists because they are no longer valid targets. Report summary.mappings_with_inactive_target (which counts an account with a dead target on EITHER dimension) alongside the completion counts and never describe such an account as settled. profit_centres_total says which zero a zero profit count is, and profit_mapped_total says what survives: when profit_centres_total is 0 the profit dimension is not in use and no account NEEDS a profit-centre policy — say that, never that the profit dimension is complete. If profit_mapped_total is also 0, no account has one either; if it is above 0 the dimension has been CLOSED and that many accounts still car…

NameTypeReqDescription
balance_bearing_onlyboolean–Return only accounts that carry a balance, without returning the balance itself.
client_idstringyesThe entity (client) id — from list_clients.
name_patternsarray–Return accounts whose code or name contains at least one of these case-insensitive patterns.
pageinteger–1-based page number (default 1).
page_sizeinteger–Rows per page (default 100, max 200).
profit_unmapped_onlyboolean–Return only accounts that still need a PROFIT-centre policy — the rows behind profit_unmapped_total. Combine with unmapped_only to get accounts that need both.
unmapped_onlyboolean–Return only accounts that still need a COST-centre policy. It does not filter on the profit dimension — use profit_unmapped_only for that.

No output schema declared.

No examples provided.

list_allocation_runs ~218

MANAGEMENT data class. Discover the latest generated persisted allocation run for each requested period and its 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: if it reports source_changed, restart at page 1. Latest generated does not establish source freshness; known_stale and not_assessed are both warnings, never a claim that the source is fresh. Raw stale reasons and warning context are not returned.

NameTypeReqDescription
client_idstringyesThe entity (client) id — from list_clients.
page_sizeinteger–Rows per source-pinned page (default 20, max 50).
page_tokenstring–Signed continuation from the prior page; restart without it if source_changed.
periodstring–Optional management month in YYYY-MM.

No output schema declared.

No examples provided.

list_budgets ~232

MANAGEMENT data class. Discover the existing ACTIVE budget for each requested Entity and fiscal year, including earlier fiscal years. Newer independent drafts and archived versions are not readable. If there is no ACTIVE budget, the native list is empty; never substitute a draft or archived row. Budget ids and versions are source citations without identity fields. Locked FX rate and all money-valued fields are decimal strings. Filter fiscal-year start before paging. The signed page_token is pinned to the complete ACTIVE source; if source_changed, discard partial results and restart discovery at page 1 without the old token. This lists budget headers only, not cells, approval identities, or a recalculated budget.

NameTypeReqDescription
client_idstringyesThe entity (client) id — from list_clients.
fiscal_year_startstring–Optional fiscal-year first-of-month date, e.g. 2026-04-01.
page_sizeinteger–Rows per source-pinned page (default 20, max 50).
page_tokenstring–Signed continuation from the prior page; restart without it if source_changed.

No output schema declared.

No examples provided.

list_chart_rebaselines ~460

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 the evidence Datavrn compares FUTURE uploads against, so wrong-entity detection for this entity is working from a smaller picture than the entity’s real chart. Each row reports how many distinctive ledger names Datavrn already held (trusted_considered), how many the upload carries (incoming_considered), how many are on both sides (matched), and the two coverage ratios. Show your user those numbers in their own terms. `shortfall` names WHICH direction fell short, and it is the part to say out loud, because the three cases are different situations to an accountant: "incoming" means most of the file is ledger names Datavrn does not already treat as evidence — the chart in the file is much larger than what Datavrn holds; "trusted" means much of what Datavrn holds is missing from the file; "both" means the two charts barely overlap either way. It is null when there was nothing to compare against at all, which the row reports as reason "empty_trust_recovery". This call only lists. To confirm one of these uploads, call preview_chart_rebaseline for that upload — it re-reads the figures and issues the approval confirm_complete_chart needs. An empty list means nothing is waiting: for almost every entity that is the normal state.

NameTypeReqDescription
client_idstringyesThe entity (client) id — from list_clients.
on_behalf_ofstring–The email address your user signs in to Datavrn with. This records who authorised the change alongside the connection that made it. REQUIRED on an API-key connection — ask your user for it, do not gu…

No output schema declared.

No examples provided.

list_clients ~40

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_cost_centres ~239

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 that create_cost_centre wrote, so a wrong parent can be seen and corrected. is_active false means the centre is DEACTIVATED: it is not an available target, never propose a mapping onto one, and never count it when you tell the user how many targets exist. Check the returned codes before choosing a code for create_cost_centre — a code must be unique among live centres. Tell the user what the existing structure means before suggesting a change.

NameTypeReqDescription
client_idstringyesThe entity (client) id — from list_clients.
pageinteger–1-based page number (default 1).
page_sizeinteger–Rows per page (default 100, max 200).

No output schema declared.

No examples provided.

list_entity_mis_runs ~220

SAVED MIS data class; requires fresh saved-MIS consent. Discover the canonical current Entity MIS for any requested reporting period, including earlier periods, using a live offset catalogue. Superseded versions are not accessible. Available sealed working, submitted and approved output is readable; approval is not required, and retrieval never approves a run. Disclose the actual approval status. Pending/running/failed/cancelled work has no saved numerical output. Use the returned physical run_id for catalogue and number reads; the returned version is a source citation, not a selector. This does not generate MIS. Group access and other report families are still being added.

NameTypeReqDescription
client_idstringyesThe entity (client) id — from list_clients.
offsetinteger–Live catalogue offset; results can change between calls.
page_sizeinteger––
period_endstring–Optional period end, YYYY-MM-DD.
period_startstring–Optional period start, YYYY-MM-DD.
periodicitystring––

No output schema declared.

No examples provided.

list_grouping_suggestions ~343

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 review of the low-confidence tail. Confirm only what your user approves via confirm_groupings. Returns a summary (counts by confidence tier) plus one page of suggestion rows — fetch tier by tier with the confidence filter instead of everything at once; pass include='confirmed' to see already-confirmed groupings.

NameTypeReqDescription
client_idstringyesThe entity (client) id — from list_clients.
confidencestring–Keep only suggestion rows in this confidence tier ('none' = accounts with no deterministic suggestion). Filters rows only — the summary counts stay over the whole population.
has_balanceboolean–Keep only suggestion rows whose account carries a live balance (true) or not (false).
includestring–Which rows to page: 'suggestions' (default), 'confirmed' (already-grouped accounts), or 'both'.
limitinteger–Page size (default 50, max 200).
offsetinteger–Rows to skip (default 0).
period_idstringyesThe reporting period id — from list_periods.
template_idstringyesThe statement template id (e.g. 'schedule3_v1' Division I; see list_snapshots/workspace).

No output schema declared.

No examples provided.

list_periods ~67

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.

NameTypeReqDescription
client_idstringyesThe entity (client) id — from list_clients.

No output schema declared.

No examples provided.

list_profit_centres ~101

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.

NameTypeReqDescription
client_idstringyesThe entity (client) id — from list_clients.
pageinteger–1-based page number (default 1).
page_sizeinteger–Rows per page (default 100, max 200).

No output schema declared.

No examples provided.

list_replacements ~346

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: within that window state is "restorable" and preview_replacement_restore/restore_replacement can put it back; after it, state is "lapsed" — the record of what happened is kept and is still listed here, but it can no longer be undone from this connection, so tell the user to contact Datavrn support if they need that data recovered. "restored" means it has already been put back. Only syncs that ran UNATTENDED are listed: a replacement someone on the team previewed and confirmed themselves is not offered for undo, by design. window_closes_at is the date the undo window shuts. If connection_attributed is false, Datavrn can no longer prove which connection made that replacement — say so rather than naming this one. To find these without a connection id, call get_pending_work: it lists every still-undoable replacement across the entities you can see, with the entity and connection to use here.

NameTypeReqDescription
client_idstringyesThe entity (client) id — from list_clients.
connection_idstringyesThe connected data source’s id — from get_pending_work’s restorable_replacements rows, or from the entity’s data-sources page in the web app.

No output schema declared.

No examples provided.

Install

How do I install the com.datavrn/schedule-iii MCP server?

com.datavrn/schedule-iii is a hosted endpoint at https://app.datavrn.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · app.datavrn.com

# add to Claude Code
claude mcp add --transport http com-datavrn-schedule-iii 'https://app.datavrn.com/api/mcp'
Common questions

What is the com.datavrn/schedule-iii MCP server?

com.datavrn/schedule-iii is an MCP server listed in the public MCP registry as com.datavrn/schedule-iii. Deterministic Schedule III statements for Indian companies: trial balance in, Excel workbook out. This page covers its hosted endpoint (https://app.datavrn.com/api/mcp).

Is the com.datavrn/schedule-iii MCP server safe to use?

com.datavrn/schedule-iii scores 89 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the com.datavrn/schedule-iii MCP server expose?

com.datavrn/schedule-iii exposes 71 tools: list_clients, create_client, upload_trial_balance, get_upload, set_header_row, and 66 more. Their descriptions and schemas cost roughly 22,929 tokens of context every time the server is loaded.

Does the com.datavrn/schedule-iii MCP server require authentication?

Yes. com.datavrn/schedule-iii asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the com.datavrn/schedule-iii MCP server still maintained?

com.datavrn/schedule-iii is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the com.datavrn/schedule-iii MCP server?

VerifyMCP ran 13 checks on com.datavrn/schedule-iii, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.