Skip to main content
Glama
zvika-finally

Marqeta DiVA API MCP Server

export_view_to_file

Export financial data views (authorizations, settlements, cards) to JSON or CSV files. Apply filters, aggregations, and field selection. Note: API limits to 10,000 records per query; use narrower date ranges for larger exports.

Instructions

Export datasets to a file (JSON or CSV). Note: DiVA API limits results to 10,000 records per query. To get more data, use narrower date ranges or more specific filters and call multiple times. Supports all view types: authorizations, settlements, clearings, declines, loads, cards, users, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
view_nameYesName of the view (e.g., 'authorizations', 'settlements', 'cards')
aggregationNoAggregation leveldetail
output_pathYesFile path where data will be written (e.g., './exports/authorizations.json')
formatNoOutput file formatjson
max_recordsNoMaximum total records to export (omit to export all matching records)
fieldsNoSpecific fields to include in export
filtersNoFilters on data fields. For date filtering, use actual date field names with operators (e.g., {'transaction_timestamp': '>=2023-10-20'})
sort_byNoField to sort by
programNoOverride default program
Behavior4/5

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

No annotations are provided, so the description bears the full burden. It discloses the API limit and suggests workarounds, providing important behavioral context. It could be more explicit about file overwriting, but the given information is adequate.

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

Conciseness5/5

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

Two concise sentences, front-loaded with the purpose, followed by a crucial behavioral note. No unnecessary words.

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

Completeness4/5

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

Given the tool's complexity (9 parameters), no output schema, and no annotations, the description covers the essential purpose, limit, and support for view types. Could mention output file handling, but overall sufficient.

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

Parameters3/5

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

Input schema has 100% description coverage, so the baseline is 3. The description adds minor value by emphasizing the limit, but the schema already explains parameters well.

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?

The description clearly states the action (Export datasets) and the resource (to a file in JSON or CSV). It lists supported view types, distinguishing it from sibling 'get_' tools that retrieve data without writing to files.

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

Usage Guidelines4/5

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

The description explicitly notes the DiVA API limit of 10,000 records and advises using narrower filters or multiple calls for more data. It implies when to use this tool (for exporting to file) without specifying explicit when-not-to-use scenarios, but the context of sibling tools makes it clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zvika-finally/marqeta-diva-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server