Create Standard Statements
create_standard_statementsRetain one exact financial source and create its complete ordered set of Standard Statements as one durable FinStat Task. Supply exactly one byte-bearing source: an authorized handle or bounded content_base64; file_name and mime_type may name it either way (a handle otherwise carries its own). The transfer program is the reliable intake: create_upload_sessions, PUT the bytes, pass the returned handle. Inline content_base64 is for small sources only — many MCP clients cap tool arguments in the tens of KB regardless of this schema's bound; if an inline call fails to leave your client, switch to the transfer program rather than shrinking the source. For a statement your agent builds (from a CSV or bank export, say), pass it as statement; the shape is this parameter's schema and guide_canonical_schema. For example: {"type": "checking", "account": {"institution": {"name": "River Bank"}, "number": "1001", "currency": "USD"}, "period": {"start": "2025-01-01", "end": "2025-01-31"}, "controls": {"beginningCents": 200000, "endingCents": 350000}, "transactions": [{"date": "2025-01-15", "description": "PAYROLL", "amountCents": 150000}]}. PDF is the normal case; canonical statement JSON bytes are accepted (exact-byte, no model), as one bare statement or several in the optional {accounts: [{statement}], sourceLabel} envelope: guide_canonical_schema gives the shape, each type's required controls and an example, and with topic csv how to build one from a CSV or bank export. What is not a fact is fixed up and listed in the result's normalized; a missing balance or rows that do not add up are refused, saying what to fix. One source may yield several Standard Statements. Persist taskId. Native clients poll tasks/get; ordinary clients poll tasks_get. Completion returns fresh expiring handles. The source bytes remain unchanged and are not returned. Exact-byte replay recovers the existing creation without another interpretation charge. Register the returned Standard Statements; nothing reaches the workspace until submit. Metered only when new interpretation runs.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| handle | No | A transfer handle naming the source bytes: the upload session's handle after the PUT, or a handle another tool returned. | |
| file_name | No | The source's file name, e.g. statement.pdf or march.json; .json reads it as canonical statement JSON. | |
| mime_type | No | The source's media type, e.g. application/pdf or application/json. | |
| statement | No | A statement your agent built (from a CSV or bank export, say), as an object: the canonical statement, exactly the shape guide_canonical_schema returns. Exclusive with handle and content_base64; read like canonical JSON bytes, fix-ups and refusals alike. | |
| workspace_tag | Yes | Active workspace id (the workspace_tag create_workspace and list_workspaces return). | |
| content_base64 | No | The source bytes inline, base64, for small files: a PDF, or canonical statement JSON (guide_canonical_schema). |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||