{"data":{"name":"com.datavrn/schedule-iii","title":null,"description":"Deterministic Schedule III statements for Indian companies: trial balance in, Excel workbook out.","version":"1.0.0","websiteUrl":"https://app.datavrn.com/agents","repositoryUrl":null,"remotes":[{"url":"https://app.datavrn.com/api/mcp","type":"streamable-http"}],"packages":[],"status":"active","isLatest":true,"publishedAt":"2026-08-06T13:11:38.079Z","updatedAt":"2026-08-06T13:11:38.079Z","source":"official-registry","verification":"official","confidence":100,"stars":null,"sources":[{"stars":null,"title":null,"source":"official-registry","sourceId":"com.datavrn/schedule-iii","updatedAt":"2026-08-06T13:11:38.079Z","confidence":100,"websiteUrl":"https://app.datavrn.com/agents","description":"Deterministic Schedule III statements for Indian companies: trial balance in, Excel workbook out.","verification":"official","repositoryUrl":null}],"toolIndex":{"tools":[{"serverName":"com.datavrn/schedule-iii","endpointFingerprint":"00fbbdc191da8716bc3a09554ab997847ffa3035c552116f8caaf8f92d23d806","name":"assert_previous_year_no_activity","title":"Record that the previous year genuinely had no activity","description":"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.","inputSchema":{"type":"object","properties":{"client_id":{"type":"string","format":"uuid","description":"The entity (client) id — from list_clients."},"template_id":{"type":"string","minLength":1,"maxLength":80,"description":"The statement template id (e.g. 'schedule3_v1' Division I; see list_snapshots/workspace)."},"period_id":{"type":"string","format":"uuid","description":"The reporting period id — from list_periods."},"reason":{"type":"string","minLength":1,"maxLength":2000,"description":"Your user’s own words: why the previous year had no activity. Recorded with the statement and shown to whoever reviews it."},"confirm_token":{"type":"string","minLength":20,"maxLength":200,"description":"The approval from get_comparative_source_state. Call it first and present its finding to your user."},"on_behalf_of":{"type":"string","format":"email","maxLength":320,"description":"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 guess. On an OAuth connection leave it out: the change is recorded as authorised by the member who connected; if you do supply it, it must be that member."}},"required":["client_id","template_id","period_id","reason","confirm_token"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"title":"Record that the previous year genuinely had no activity","readOnlyHint":false,"destructiveHint":false,"openWorldHint":false},"definitionHash":"24291824ea0c01a9e16fd3fce7a50aca10bf8509be227b7840bb926724a41d93","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-15T09:46:03.082Z","metadataTrust":"untrusted"},{"serverName":"com.datavrn/schedule-iii","endpointFingerprint":"00fbbdc191da8716bc3a09554ab997847ffa3035c552116f8caaf8f92d23d806","name":"close_incomplete_mis_capture","title":"Close incomplete generation","description":"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.","inputSchema":{"type":"object","properties":{"run_id":{"type":"string","format":"uuid","description":"The exact incomplete MIS run id the user chose to close."},"on_behalf_of":{"type":"string","format":"email","maxLength":320,"description":"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 guess. On an OAuth connection leave it out: the change is recorded as authorised by the member who connected; if you do supply it, it must be that member."}},"required":["run_id"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"title":"Close incomplete generation","readOnlyHint":false,"destructiveHint":true,"openWorldHint":false},"definitionHash":"ed236c38122718cb7d6c7a0230083c4990f01accd26fb9dee5d8dbbda9097209","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-15T09:46:03.082Z","metadataTrust":"untrusted"},{"serverName":"com.datavrn/schedule-iii","endpointFingerprint":"00fbbdc191da8716bc3a09554ab997847ffa3035c552116f8caaf8f92d23d806","name":"confirm_capture_review","title":"Confirm a section has been reviewed","description":"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.","inputSchema":{"type":"object","properties":{"client_id":{"type":"string","format":"uuid","description":"The entity (client) id — from list_clients."},"template_id":{"type":"string","minLength":1,"maxLength":80},"period_id":{"type":"string","format":"uuid"},"capture_kind":{"type":"string","enum":["adjustments","prior_year_values","asset_movements","provision_movements","reserves_movements","share_capital","partner_capital","settings","disclosures"]},"reason_code":{"type":"string","enum":["comparative_reviewed_complete","disclosures_reviewed_complete"]},"note":{"type":"string","minLength":1,"maxLength":2000},"on_behalf_of":{"type":"string","format":"email","maxLength":320,"description":"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 guess. On an OAuth connection leave it out: the change is recorded as authorised by the member who connected; if you do supply it, it must be that member."}},"required":["client_id","template_id","period_id","capture_kind","reason_code"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"title":"Confirm a section has been reviewed","readOnlyHint":false,"destructiveHint":true,"openWorldHint":false},"definitionHash":"eed4c3433dd80ad93e562f00f50dad45b0606ebeecbaaa82e358b534fafb733e","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-15T09:46:03.082Z","metadataTrust":"untrusted"},{"serverName":"com.datavrn/schedule-iii","endpointFingerprint":"00fbbdc191da8716bc3a09554ab997847ffa3035c552116f8caaf8f92d23d806","name":"confirm_column_mapping","title":"Confirm column mapping","description":"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.","inputSchema":{"type":"object","properties":{"upload_id":{"type":"string","format":"uuid","description":"The upload session id returned by upload_trial_balance."},"mapping":{"type":"object","additionalProperties":{"type":"string","minLength":1}},"options":{"type":"object","properties":{"eligible_fte_source_binding":{"type":"object","properties":{"version":{"type":"string","const":"eligible-fte-source-binding/v1"},"contractor_scope_evidence_snapshot_id":{"type":"string","pattern":"^[0-9a-f]{8}-[0-9a-f]{4}-[1-5][0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$"},"roster_source_snapshot_id":{"anyOf":[{"$ref":"#/properties/options/properties/eligible_fte_source_binding/properties/contractor_scope_evidence_snapshot_id"},{"type":"null"}]}},"required":["version","contractor_scope_evidence_snapshot_id"],"additionalProperties":false},"number_format":{"type":"string","enum":["comma_grouped","european"]},"date_format":{"type":"string","enum":["DMY","MDY"]},"party_type":{"type":"string","enum":["receivable","payable"]},"buckets":{"type":"array","items":{"type":"string","minLength":1,"maxLength":40},"minItems":1,"maxItems":20},"pnl_basis":{"type":"string","enum":["period_activity","cumulative_fy"]},"wide":{"type":"boolean"},"basis_confirmed":{"type":"boolean"},"as_at_date":{"type":"string","minLength":1,"maxLength":40},"period_start":{"type":"string","minLength":1,"maxLength":40},"declared_from":{"type":"string","pattern":"^\\d{4}-\\d{2}-\\d{2}$"},"declared_to":{"type":"string","pattern":"^\\d{4}-\\d{2}-\\d{2}$"}},"additionalProperties":false},"save_as":{"type":"string","minLength":1,"maxLength":120}},"required":["upload_id","mapping"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"title":"Confirm column mapping","readOnlyHint":false,"destructiveHint":true,"openWorldHint":false},"definitionHash":"8f375016e18238607c903f2afc87c62f45ab32bfc48b20a1c4e831ca68001092","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-15T09:46:03.082Z","metadataTrust":"untrusted"},{"serverName":"com.datavrn/schedule-iii","endpointFingerprint":"00fbbdc191da8716bc3a09554ab997847ffa3035c552116f8caaf8f92d23d806","name":"confirm_groupings","title":"Confirm account groupings","description":"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.","inputSchema":{"type":"object","properties":{"client_id":{"type":"string","format":"uuid","description":"The entity (client) id — from list_clients."},"template_id":{"type":"string","minLength":1,"maxLength":80},"decisions":{"type":"array","items":{"type":"object","properties":{"account_id":{"type":"string","format":"uuid"},"leaf_code":{"anyOf":[{"type":"string","minLength":1,"maxLength":80},{"type":"null"}]},"is_cash_equivalent":{"type":["boolean","null"]},"suggested_reason":{"type":"string","minLength":1,"maxLength":400},"suggested_confidence":{"type":"string","enum":["high","medium","low"]}},"required":["account_id","leaf_code"],"additionalProperties":false},"minItems":1,"maxItems":2000},"grouping_version":{"type":"integer","minimum":0},"removal_token":{"type":"string","minLength":20,"maxLength":200},"removal_count":{"type":"integer","minimum":1,"maximum":2000}},"required":["client_id","template_id","decisions"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"title":"Confirm account groupings","readOnlyHint":false,"destructiveHint":true,"openWorldHint":false},"definitionHash":"aecee8dcf820994c3e36f32bbb0c4b90df3a1bbd44f0c881a20e2cffc946a30f","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-15T09:46:03.082Z","metadataTrust":"untrusted"},{"serverName":"com.datavrn/schedule-iii","endpointFingerprint":"00fbbdc191da8716bc3a09554ab997847ffa3035c552116f8caaf8f92d23d806","name":"copy_capture_declarations","title":"Copy last period’s capture answers","description":"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.","inputSchema":{"type":"object","properties":{"client_id":{"type":"string","format":"uuid","description":"The entity (client) id — from list_clients."},"template_id":{"type":"string","minLength":1,"maxLength":80},"period_id":{"type":"string","format":"uuid"},"on_behalf_of":{"type":"string","format":"email","maxLength":320,"description":"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 guess. On an OAuth connection leave it out: the change is recorded as authorised by the member who connected; if you do supply it, it must be that member."}},"required":["client_id","template_id","period_id"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"title":"Copy last period’s capture answers","readOnlyHint":false,"destructiveHint":false,"openWorldHint":false},"definitionHash":"d94e130e3bd74b288599e375e7e3ff062b5e429ad5026770a56786c0c20c7677","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-15T09:46:03.082Z","metadataTrust":"untrusted"},{"serverName":"com.datavrn/schedule-iii","endpointFingerprint":"00fbbdc191da8716bc3a09554ab997847ffa3035c552116f8caaf8f92d23d806","name":"create_client","title":"Create entity","description":"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.","inputSchema":{"type":"object","properties":{"name":{"type":"string","minLength":1,"maxLength":200},"business_model_code":{"anyOf":[{"type":"string","minLength":1},{"type":"null"}]}},"required":["name"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"title":"Create entity","readOnlyHint":false,"destructiveHint":false,"openWorldHint":false},"definitionHash":"a16a248f37e9716537e67a1a013efac1bcdaed6de749912bf05ee4561344de7f","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-15T09:46:03.082Z","metadataTrust":"untrusted"},{"serverName":"com.datavrn/schedule-iii","endpointFingerprint":"00fbbdc191da8716bc3a09554ab997847ffa3035c552116f8caaf8f92d23d806","name":"create_upload_link","title":"Create upload link","description":"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.","inputSchema":{"type":"object","properties":{"client_id":{"type":"string","format":"uuid","description":"The entity (client) id — from list_clients."},"file_name":{"type":"string","minLength":1,"maxLength":255,"description":"The file the user is expected to upload, e.g. 'tb-2026-03.xlsx' (shown on the upload page)."},"format":{"type":"string","description":"Leave unset — the assistant handles Trial Balances only; any other format is refused (use the Datavrn web app)."},"source":{"type":"string","description":"Set 'tally_file' when the file is a Tally xlsx export; omit otherwise."}},"required":["client_id","file_name"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"title":"Create upload link","readOnlyHint":false,"destructiveHint":false,"openWorldHint":false},"definitionHash":"65cede4cb8d77f1131e594e810bb39c0728d1274c86d2aa2acf6be7515e2dc96","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-15T09:46:03.082Z","metadataTrust":"untrusted"},{"serverName":"com.datavrn/schedule-iii","endpointFingerprint":"00fbbdc191da8716bc3a09554ab997847ffa3035c552116f8caaf8f92d23d806","name":"declare_capture_na","title":"Record nothing to report, or not applicable","description":"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.","inputSchema":{"type":"object","properties":{"client_id":{"type":"string","format":"uuid","description":"The entity (client) id — from list_clients."},"template_id":{"type":"string","minLength":1,"maxLength":80},"period_id":{"type":"string","format":"uuid"},"capture_kind":{"type":"string","enum":["adjustments","prior_year_values","asset_movements","provision_movements","reserves_movements","share_capital","partner_capital","settings","disclosures"]},"reason_code":{"type":"string","enum":["first_year","no_activity","not_applicable"]},"note":{"type":"string","minLength":1,"maxLength":2000},"on_behalf_of":{"type":"string","format":"email","maxLength":320,"description":"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 guess. On an OAuth connection leave it out: the change is recorded as authorised by the member who connected; if you do supply it, it must be that member."}},"required":["client_id","template_id","period_id","capture_kind","reason_code"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"title":"Record nothing to report, or not applicable","readOnlyHint":false,"destructiveHint":true,"openWorldHint":false},"definitionHash":"77e1140017672f84c24be72a47ce1c4c0057e8b1c74e52637abf57900f4fbab2","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-15T09:46:03.082Z","metadataTrust":"untrusted"},{"serverName":"com.datavrn/schedule-iii","endpointFingerprint":"00fbbdc191da8716bc3a09554ab997847ffa3035c552116f8caaf8f92d23d806","name":"finalise_statement","title":"Seal the permanent client copy of a version","description":"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.","inputSchema":{"type":"object","properties":{"client_id":{"type":"string","format":"uuid","description":"The entity (client) id — from list_clients."},"snapshot_id":{"type":"string","format":"uuid"},"acknowledgments":{"type":"object","properties":{"advisory_labels":{"type":"array","items":{"type":"string","minLength":1,"maxLength":500},"maxItems":50},"pending_input_count":{"type":"integer","minimum":0},"reason":{"type":"string","minLength":1,"maxLength":500}},"required":["advisory_labels","pending_input_count"],"additionalProperties":false},"confirm_token":{"type":"string","minLength":20,"maxLength":200},"on_behalf_of":{"type":"string","format":"email","maxLength":320,"description":"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 guess. On an OAuth connection leave it out: the change is recorded as authorised by the member who connected; if you do supply it, it must be that member."}},"required":["client_id","snapshot_id","acknowledgments","confirm_token"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"title":"Seal the permanent client copy of a version","readOnlyHint":false,"destructiveHint":true,"openWorldHint":false},"definitionHash":"22898121daa4ad914473ccd916c973e7f04fffb9d408f3c178ce7d2da66fefed","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-15T09:46:03.082Z","metadataTrust":"untrusted"},{"serverName":"com.datavrn/schedule-iii","endpointFingerprint":"00fbbdc191da8716bc3a09554ab997847ffa3035c552116f8caaf8f92d23d806","name":"generate_schedule_iii","title":"Generate Schedule III statements","description":"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.","inputSchema":{"type":"object","properties":{"client_id":{"type":"string","format":"uuid","description":"The entity (client) id — from list_clients."},"request_id":{"type":"string","format":"uuid"},"template_id":{"type":"string","minLength":1,"maxLength":80},"period_id":{"type":"string","format":"uuid"},"acknowledge_unclassified":{"type":"boolean"},"acknowledge_count":{"type":"integer","minimum":0},"acknowledge_reason":{"type":"string","minLength":1,"maxLength":500},"acknowledge_multi_month_pnl":{"type":"boolean"},"acknowledge_month_count":{"type":"integer","minimum":0}},"required":["client_id","template_id","period_id"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"title":"Generate Schedule III statements","readOnlyHint":false,"destructiveHint":false,"openWorldHint":false},"definitionHash":"9347679398e20f1c76821602087e10b4d9b523b24cf87f241d86e664b521cd38","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-15T09:46:03.082Z","metadataTrust":"untrusted"},{"serverName":"com.datavrn/schedule-iii","endpointFingerprint":"00fbbdc191da8716bc3a09554ab997847ffa3035c552116f8caaf8f92d23d806","name":"get_allocation_account_figures","title":"Read allocation account figures","description":"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.","inputSchema":{"type":"object","properties":{"client_id":{"type":"string","format":"uuid","description":"The entity (client) id — from list_clients."},"period":{"type":"string","pattern":"^\\d{4}-(0[1-9]|1[0-2])$","description":"Management month in YYYY-MM."},"allocation_dimension":{"type":"string","enum":["cost","profit"],"description":"Required partition: cost for cost-centre or step-down questions; profit for profit-centre questions. Do not add the two views."},"account_name_patterns":{"type":"array","items":{"type":"string","minLength":1,"maxLength":80},"maxItems":10,"description":"Up to 10 case-insensitive account-name substrings; any match is retained."},"min_abs_mis":{"type":"string","pattern":"^\\d{1,16}(\\.\\d{1,2})?$","description":"Minimum absolute MIS figure in rupees as a decimal string, e.g. '100000'."},"page_size":{"type":"integer","minimum":1,"maximum":200,"description":"Rows per source-pinned page (default 50, max 200)."},"page_token":{"type":"string","minLength":1,"maxLength":4096,"description":"Signed continuation from the prior page; restart without it if source_changed."}},"required":["client_id","period","allocation_dimension"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"title":"Read allocation account figures","readOnlyHint":true,"destructiveHint":false,"openWorldHint":false},"definitionHash":"ecadf891ad2bb36e749178ced2d960e5a09c1d39cc5910d20b1f8684b8d9f3ec","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-15T09:46:03.082Z","metadataTrust":"untrusted"},{"serverName":"com.datavrn/schedule-iii","endpointFingerprint":"00fbbdc191da8716bc3a09554ab997847ffa3035c552116f8caaf8f92d23d806","name":"get_allocation_target_figures","title":"Read allocation target figures","description":"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.","inputSchema":{"type":"object","properties":{"client_id":{"type":"string","format":"uuid","description":"The entity (client) id — from list_clients."},"period":{"type":"string","pattern":"^\\d{4}-(0[1-9]|1[0-2])$","description":"Management month in YYYY-MM."},"allocation_dimension":{"type":"string","enum":["cost","profit"],"description":"Required partition: cost for cost-centre or step-down questions; profit for profit-centre questions. Do not add the two views."},"account_name_patterns":{"type":"array","items":{"type":"string","minLength":1,"maxLength":80},"maxItems":10,"description":"Up to 10 case-insensitive account-name substrings; any match is retained."},"target_types":{"type":"array","items":{"type":"string","enum":["cost_centre","sub_cost_centre","profit_centre","sub_profit_centre","unallocated"]},"maxItems":5,"description":"Restrict to allocation target types."},"allocation_sources":{"type":"array","items":{"type":"string","enum":["account_mapping","source_dimension","unallocated","step_down"]},"maxItems":4,"description":"Restrict to allocation sources."},"min_abs_amount":{"type":"string","pattern":"^\\d{1,16}(\\.\\d{1,2})?$","description":"Minimum absolute allocated amount in rupees as a decimal string, e.g. '100000'."},"page_size":{"type":"integer","minimum":1,"maximum":200,"description":"Rows per source-pinned page (default 50, max 200)."},"page_token":{"type":"string","minLength":1,"maxLength":4096,"description":"Signed continuation from the prior page; restart without it if source_changed."}},"required":["client_id","period","allocation_dimension"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"title":"Read allocation target figures","readOnlyHint":true,"destructiveHint":false,"openWorldHint":false},"definitionHash":"da0bbdf1554182f095ca6b79713a9b3cc04f21e89e323b7228eb0b8ba043907c","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-15T09:46:03.082Z","metadataTrust":"untrusted"},{"serverName":"com.datavrn/schedule-iii","endpointFingerprint":"00fbbdc191da8716bc3a09554ab997847ffa3035c552116f8caaf8f92d23d806","name":"get_budget","title":"Read budget","description":"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 grand total, so no cross-line grand total is exposed. No people, ownership, editability, or approval identities are returned.","inputSchema":{"type":"object","properties":{"client_id":{"type":"string","format":"uuid","description":"The entity (client) id — from list_clients."},"budget_id":{"type":"string","format":"uuid","description":"Budget id from list_budgets."},"month":{"type":"string","pattern":"^\\d{4}-(0[1-9]|1[0-2])$","description":"Optional budget month in YYYY-MM."},"line_codes":{"type":"array","items":{"type":"string","minLength":1,"maxLength":80},"maxItems":25,"description":"Up to 25 P&L line codes."},"cost_centre_ids":{"type":"array","items":{"type":"string","minLength":1,"maxLength":80},"maxItems":25,"description":"Up to 25 cost-centre ids."},"inference":{"type":"string","enum":["all","entered","inferred"],"description":"Cell inference state (default all)."},"page_size":{"type":"integer","minimum":1,"maximum":200,"description":"Cells per source-pinned page (default 100, max 200)."},"page_token":{"type":"string","minLength":1,"maxLength":4096,"description":"Signed continuation from the prior page; restart without it if source_changed."}},"required":["client_id","budget_id"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"title":"Read budget","readOnlyHint":true,"destructiveHint":false,"openWorldHint":false},"definitionHash":"0ff9607e422320ef51b3934fcbef312be14df0e353a73aae5898c6e43032bdfb","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-15T09:46:03.082Z","metadataTrust":"untrusted"},{"serverName":"com.datavrn/schedule-iii","endpointFingerprint":"00fbbdc191da8716bc3a09554ab997847ffa3035c552116f8caaf8f92d23d806","name":"get_comparative_source_state","title":"Check the previous-year comparative source","description":"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.","inputSchema":{"type":"object","properties":{"client_id":{"type":"string","format":"uuid","description":"The entity (client) id — from list_clients."},"template_id":{"type":"string","minLength":1,"maxLength":80,"description":"The statement template id (e.g. 'schedule3_v1' Division I; see list_snapshots/workspace)."},"period_id":{"type":"string","format":"uuid","description":"The reporting period id — from list_periods."},"on_behalf_of":{"type":"string","format":"email","maxLength":320,"description":"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 guess. On an OAuth connection leave it out: the change is recorded as authorised by the member who connected; if you do supply it, it must be that member."}},"required":["client_id","template_id","period_id"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"title":"Check the previous-year comparative source","readOnlyHint":false,"destructiveHint":false,"openWorldHint":false},"definitionHash":"39ab60954ecc902676ed20fe2edd28db10e48e57ae0370db117d6cf79d5a8518","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-15T09:46:03.082Z","metadataTrust":"untrusted"},{"serverName":"com.datavrn/schedule-iii","endpointFingerprint":"00fbbdc191da8716bc3a09554ab997847ffa3035c552116f8caaf8f92d23d806","name":"get_finalise_readiness","title":"Check finalisation state and get approval","description":"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.","inputSchema":{"type":"object","properties":{"client_id":{"type":"string","format":"uuid","description":"The entity (client) id — from list_clients."},"snapshot_id":{"type":"string","format":"uuid","description":"The statement version id — from list_snapshots or get_schedule3_workspace."},"on_behalf_of":{"type":"string","format":"email","maxLength":320,"description":"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 guess. On an OAuth connection leave it out: the change is recorded as authorised by the member who connected; if you do supply it, it must be that member."}},"required":["client_id","snapshot_id"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"title":"Check finalisation state and get approval","readOnlyHint":false,"destructiveHint":false,"openWorldHint":false},"definitionHash":"6f49525016a7557642acd0d8b090a8a7848819a10052f38fe9498bd83bc8cf3f","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-15T09:46:03.082Z","metadataTrust":"untrusted"},{"serverName":"com.datavrn/schedule-iii","endpointFingerprint":"00fbbdc191da8716bc3a09554ab997847ffa3035c552116f8caaf8f92d23d806","name":"get_job","title":"Get job status","description":"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.","inputSchema":{"type":"object","properties":{"job_id":{"type":"string","format":"uuid","description":"The job id returned by generate_schedule_iii."}},"required":["job_id"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"title":"Get job status","readOnlyHint":true,"destructiveHint":false,"openWorldHint":false},"definitionHash":"a0b345feca82a9b92d00ba09c26db5ff1b74b822b699362bc41ac97d8a4dc26e","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-15T09:46:03.082Z","metadataTrust":"untrusted"},{"serverName":"com.datavrn/schedule-iii","endpointFingerprint":"00fbbdc191da8716bc3a09554ab997847ffa3035c552116f8caaf8f92d23d806","name":"get_partner_capital","title":"Read partner or owner capital schedule","description":"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.","inputSchema":{"type":"object","properties":{"client_id":{"type":"string","format":"uuid","description":"The entity (client) id — from list_clients."},"template_id":{"type":"string","minLength":1,"maxLength":80,"description":"The statement template id (e.g. 'schedule3_v1' Division I; see list_snapshots/workspace)."},"period_id":{"type":"string","format":"uuid","description":"The reporting period id — from list_periods."},"account_kind":{"type":"string","enum":["capital","current"],"description":"Limit to one section: 'capital' is Note 3a, 'current' is Note 3b. Omit for both."},"limit":{"type":"integer","minimum":1,"maximum":200,"description":"Page size (default 50, max 200)."},"offset":{"type":"integer","minimum":0,"description":"Rows to skip (default 0)."}},"required":["client_id","template_id","period_id"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"title":"Read partner or owner capital schedule","readOnlyHint":true,"destructiveHint":false,"openWorldHint":false},"definitionHash":"8d0aae22ad1e391308705a6a728915caa881f79da8008cdfce41ff394e60c618","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-15T09:46:03.082Z","metadataTrust":"untrusted"},{"serverName":"com.datavrn/schedule-iii","endpointFingerprint":"00fbbdc191da8716bc3a09554ab997847ffa3035c552116f8caaf8f92d23d806","name":"get_pending_work","title":"List pending work across entities","description":"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).","inputSchema":{"type":"object","properties":{"period_label":{"type":"string","description":"Reporting period label, e.g. '2026-03'; omit to default to the period most of your entities have a trial balance for."}},"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"title":"List pending work across entities","readOnlyHint":true,"destructiveHint":false,"openWorldHint":false},"definitionHash":"60cb0756e334b23469edca83e9d32f3113972e3785140889a564a17954358dd8","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-15T09:46:03.082Z","metadataTrust":"untrusted"},{"serverName":"com.datavrn/schedule-iii","endpointFingerprint":"00fbbdc191da8716bc3a09554ab997847ffa3035c552116f8caaf8f92d23d806","name":"get_schedule3_workspace","title":"Get Schedule III workspace","description":"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.","inputSchema":{"type":"object","properties":{"client_id":{"type":"string","format":"uuid","description":"The entity (client) id — from list_clients."},"template_id":{"type":"string","minLength":1,"maxLength":80,"description":"The statement template id (e.g. 'schedule3_v1' Division I; see list_snapshots/workspace)."},"period_id":{"type":"string","format":"uuid","description":"The reporting period id — from list_periods."}},"required":["client_id","template_id","period_id"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"title":"Get Schedule III workspace","readOnlyHint":true,"destructiveHint":false,"openWorldHint":false},"definitionHash":"96cf99c9e511f07f4f2887bbe5ccf19a75821b74278ad48a852634645c492848","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-15T09:46:03.082Z","metadataTrust":"untrusted"},{"serverName":"com.datavrn/schedule-iii","endpointFingerprint":"00fbbdc191da8716bc3a09554ab997847ffa3035c552116f8caaf8f92d23d806","name":"get_spreading_reconciliation","title":"Read spreading reconciliation","description":"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.","inputSchema":{"type":"object","properties":{"client_id":{"type":"string","format":"uuid","description":"The entity (client) id — from list_clients."},"period":{"type":"string","pattern":"^\\d{4}-(0[1-9]|1[0-2])$","description":"Management month in YYYY-MM."},"view":{"type":"string","enum":["accounts","adjustments"],"description":"accounts (default) or adjustments; adjustments requires account_id."},"account_id":{"type":"string","format":"uuid","description":"Required for adjustments view; an account in this entity and run."},"account_name_patterns":{"type":"array","items":{"type":"string","minLength":1,"maxLength":80},"maxItems":10,"description":"Up to 10 case-insensitive account-name substrings; any match is retained."},"page_size":{"type":"integer","minimum":1,"maximum":200,"description":"Rows per source-pinned page: accounts default 25/max 100; adjustments default 50/max 200."},"page_token":{"type":"string","minLength":1,"maxLength":4096,"description":"Signed continuation from the prior page; restart without it if source_changed."}},"required":["client_id","period"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"title":"Read spreading reconciliation","readOnlyHint":true,"destructiveHint":false,"openWorldHint":false},"definitionHash":"7a2f17f4f220db006684e5dca72b99454788034f98227a7f9ce6853883465521","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-15T09:46:03.082Z","metadataTrust":"untrusted"},{"serverName":"com.datavrn/schedule-iii","endpointFingerprint":"00fbbdc191da8716bc3a09554ab997847ffa3035c552116f8caaf8f92d23d806","name":"get_statement_figures","title":"Read statement figures","description":"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.","inputSchema":{"type":"object","properties":{"client_id":{"type":"string","format":"uuid","description":"The entity (client) id — from list_clients."},"template_id":{"type":"string","minLength":1,"maxLength":80,"description":"The statement template id (e.g. 'schedule3_v1' Division I; see list_snapshots/workspace)."},"period_id":{"type":"string","format":"uuid","description":"The reporting period id — from list_periods."},"version":{"type":"integer","minimum":1,"description":"A specific statement version; omit for the latest."}},"required":["client_id","template_id","period_id"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"title":"Read statement figures","readOnlyHint":true,"destructiveHint":false,"openWorldHint":false},"definitionHash":"60e64382ec0c278e6db8164940ab586bd6ff6708a7d9d78cb3a2bbb2d7028627","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-15T09:46:03.082Z","metadataTrust":"untrusted"},{"serverName":"com.datavrn/schedule-iii","endpointFingerprint":"00fbbdc191da8716bc3a09554ab997847ffa3035c552116f8caaf8f92d23d806","name":"get_statement_notes","title":"Read statement notes","description":"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.","inputSchema":{"type":"object","properties":{"client_id":{"type":"string","format":"uuid","description":"The entity (client) id — from list_clients."},"template_id":{"type":"string","minLength":1,"maxLength":80,"description":"The statement template id (e.g. 'schedule3_v1' Division I; see list_snapshots/workspace)."},"period_id":{"type":"string","format":"uuid","description":"The reporting period id — from list_periods."},"version":{"type":"integer","minimum":1,"description":"A specific statement version; omit for the latest."},"note_numbers":{"type":"array","items":{"type":["string","number"]},"description":"Specific note numbers to fetch (from note_index); omit for all notes."},"lines_page":{"type":"integer","minimum":1,"description":"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)."}},"required":["client_id","template_id","period_id"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"title":"Read statement notes","readOnlyHint":true,"destructiveHint":false,"openWorldHint":false},"definitionHash":"af4fcb703e4e2c27189951d3b75a7210997f659fbce80274222ac84554d26c15","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-15T09:46:03.082Z","metadataTrust":"untrusted"},{"serverName":"com.datavrn/schedule-iii","endpointFingerprint":"00fbbdc191da8716bc3a09554ab997847ffa3035c552116f8caaf8f92d23d806","name":"get_tb_rows","title":"Read trial-balance source data","description":"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.","inputSchema":{"type":"object","properties":{"client_id":{"type":"string","format":"uuid","description":"The entity (client) id — from list_clients."},"period_id":{"type":"string","format":"uuid","description":"The reporting period id — from list_periods."},"name_patterns":{"type":"array","items":{"type":"string","minLength":1,"maxLength":80},"maxItems":10,"description":"Up to 10 case-insensitive substrings; an account matches if its name contains ANY of them (e.g. ['gst','tds'])."},"side":{"type":"string","enum":["debit","credit"],"description":"Keep only accounts whose net balance falls on this side (debit = debits exceed credits). Accounts netting to zero match neither."},"min_abs_balance":{"type":"string","pattern":"^\\d{1,16}(\\.\\d{1,2})?$","description":"Keep only accounts whose balance (the larger of its debit/credit) is at least this many rupees — a decimal string like '100000'."},"page":{"type":"integer","minimum":1,"description":"1-based page number (default 1)."},"page_size":{"type":"integer","minimum":1,"maximum":500,"description":"Rows per page (default 50, max 500 — prefer filters over big pages)."}},"required":["client_id","period_id"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"title":"Read trial-balance source data","readOnlyHint":true,"destructiveHint":false,"openWorldHint":false},"definitionHash":"c4e40efaf90693ebc0a974756f6c9a315626cf928f9bd706fb9679886fc84b9d","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-15T09:46:03.082Z","metadataTrust":"untrusted"},{"serverName":"com.datavrn/schedule-iii","endpointFingerprint":"00fbbdc191da8716bc3a09554ab997847ffa3035c552116f8caaf8f92d23d806","name":"get_upload","title":"Get upload status","description":"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.","inputSchema":{"type":"object","properties":{"upload_id":{"type":"string","format":"uuid","description":"The upload session id returned by upload_trial_balance."}},"required":["upload_id"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"title":"Get upload status","readOnlyHint":true,"destructiveHint":false,"openWorldHint":false},"definitionHash":"b255a55658b69f230100feffb0c7f295dd39cd65a997c5cda45a6232efb0bd47","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-15T09:46:03.082Z","metadataTrust":"untrusted"}],"endpoints":[{"endpointFingerprint":"00fbbdc191da8716bc3a09554ab997847ffa3035c552116f8caaf8f92d23d806","protocol":"streamable-http","status":"indexed","toolCount":50,"observedAt":"2026-11-15T09:46:03.082Z"}],"authentication":"unknown"},"connectionConfigurations":{"status":"ready","authentication":"not embedded","clients":{"Claude Desktop":{"mcpServers":{"com.datavrn/schedule-iii":{"url":"https://app.datavrn.com/api/mcp"}}},"Cursor":{"mcpServers":{"com.datavrn/schedule-iii":{"url":"https://app.datavrn.com/api/mcp"}}},"VS Code":{"servers":{"com.datavrn/schedule-iii":{"type":"http","url":"https://app.datavrn.com/api/mcp"}}}}},"resourceType":"mcp-server","callable":true,"runtime":{"callable":true,"protocols":["mcp"]},"interfaces":[{"protocol":"mcp","transport":"streamable-http","url":"https://app.datavrn.com/api/mcp"}],"profile":{"apiVersion":"1","schemaVersion":"1","id":"mcp-server:com.datavrn%2Fschedule-iii","resourceType":"mcp-server","canonicalUrl":"https://www.agentsjunction.com/api/v1/servers/com.datavrn%2Fschedule-iii","name":"com.datavrn/schedule-iii","description":"Deterministic Schedule III statements for Indian companies: trial balance in, Excel workbook out.","interfaces":[{"protocol":"mcp","transport":"streamable-http","url":"https://app.datavrn.com/api/mcp"}],"capabilities":[],"identity":{"source":"official-registry","websiteUrl":"https://app.datavrn.com/agents","repositoryUrl":null,"version":"1.0.0"},"verification":{"state":"official","confidence":100},"operations":{"resourceType":"mcp-server","name":"com.datavrn/schedule-iii","status":"online","lastCheckedAt":"2026-11-20T06:17:45.766Z","lastSuccessfulCheck":"2026-11-20T06:17:45.766Z","latencyMs":344,"consecutiveFailures":0,"isStale":false,"checks":{"endpointReachable":true,"protocolValid":true,"agentCardValid":null,"mcpHandshakeValid":true},"lastSeen":null,"lastSuccessfulInteraction":null,"lastHealthCheck":"2026-11-20T06:17:45.766Z","source":{"type":"health-check","url":null},"observedAt":"2026-11-20T06:17:45.766Z"},"security":null,"timestamps":{"createdAt":"2026-08-06T13:11:38.079Z","updatedAt":"2026-08-06T13:11:38.079Z","observedAt":"2026-11-20T06:17:45.766Z"},"compatibility":{"serverVersion":"1.0.0","protocolVersions":[{"protocol":"mcp","version":null}]}}}}