com.datavrn/schedule-iii
v1.0.0Deterministic Schedule III statements for Indian companies: trial balance in, Excel workbook out.
Endpoint health
online- Last checked
- 11/20/2026, 6:17:45 AM
- Latency
- 344 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.datavrn%2Fschedule-iii
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.datavrn/schedule-iii": {
"url": "https://app.datavrn.com/api/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
25 shown · authentication unknown
Record that the previous year genuinely had no activity
assert_previous_year_no_activity
Record your user’s assertion that the previous year genuinely had no activity, so this statement’s all-nil previous-year Profit and Loss is a fact rather than a closing-entry artefact. This clears Datavrn’s refusal to finalise it. THIS IS A PROFESSIONAL ASSERTION ABOUT A CLIENT’S ACCOUNTS, RECORDED IN THE NAMED MEMBER’S NAME AND KEPT WITH THE STATEMENT. Only send it when your user has told you, in 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.
Schema valid · SHA-256 24291824ea0c…
View input schema
{ "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#" }
Connections
streamable-http
https://app.datavrn.com/api/mcp