finance

Reports: Export all data (accounts + transactions)

export_all_data

Read-onlyIdempotent

    Export the user's full data set — all accounts + all transactions —
    as CSV strings plus a base64-encoded ZIP bundle. Premium-only.

    Parity with the REST ``/api/v1/data/export_all/`` ZIP download. The
    per-resource account and transaction CSV exports are free; this
    Premium "export everything" call bundles both in one response.
    ``zip_base64`` decodes to a real .zip file; the CSV strings are
    readable directly.

    Returns:
        ``{"success": True, "accounts_csv": "...", "transactions_csv":
        "...", "zip_base64": "...", "filename": "zoninga_export_YYYY-MM-DD.zip",
        "account_count": N, "transaction_count": M}``, or
        ``{"error": "..."}`` if not Premium.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_all_data"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 22, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly/idempotent/non-destructive, but the description adds behavior beyond them: the Premium-only gate, the error shape returned when the user is not Premium, and the fact that zip_base64 decodes to a real .zip while the CSV strings are directly readable. That is real, non-redundant context for a zero-parameter export.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and scope in the first sentence, followed by the Premium/parity caveat and a structured Returns block. Slightly verbose with backtick formatting and the REST-parity sentence, but every sentence carries useful information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description carries the return contract itself and does so fully: success payload fields, the filename pattern, counts, and the error case. An agent has everything needed to call and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so the baseline is 4; there is nothing for the schema to document and nothing the description needs to compensate for. No parameter-related guidance is missing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource with explicit scope: the user's full data set (all accounts + all transactions) delivered as CSV strings plus a base64 ZIP. It also names the exact sibling alternatives (export_accounts_csv / export_transactions_csv) and explains how this tool differs from them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells the agent when to pick this over the free per-resource exports ('The per-resource account and transaction CSV exports are free; this Premium "export everything" call bundles both in one response') and discloses the Premium precondition. Nothing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All finance tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?