Skip to main content
Glama
zvika-finally

Marqeta DiVA API MCP Server

get_loads

Retrieve load transaction data with amounts and details. Filter by date ranges, aggregation levels (day, week, month), and specific fields. Note: API limits to 10,000 records; use narrower filters for larger datasets.

Instructions

Get load transaction data. Includes load amounts and transaction details. Note: DiVA API limits results to 10,000 records per query. Use narrower date ranges or more specific filters for larger datasets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aggregationNoAggregation level for the datadetail
fieldsNoSpecific fields to return
filtersNoFilters on data fields. For date filtering, use actual date field names with operators (e.g., {'post_date': '>=2023-10-20'})
sort_byNoField to sort by
countNoMaximum records to return (up to 10,000, default 10,000)
programNoOverride default program
Behavior3/5

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

Discloses the 10,000 record API limit, which is helpful. Lacks details on read-only nature, authentication needs, or side effects. With no annotations, the description carries the burden but only partially covers behavioral context.

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?

Two concise sentences, front-loaded with purpose. The second sentence adds valuable information. No wasted words.

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

Completeness2/5

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

No output schema, and description only vaguely mentions 'load amounts and transaction details'. For a tool with 6 parameters and nested objects, this is insufficient. Agent cannot infer what data is returned or how filters apply.

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?

Schema description coverage is 100%, so baseline is 3. Description adds little beyond schema; the limit warning is tangentially related to the 'count' parameter but does not enhance understanding of each parameter's meaning.

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

Purpose4/5

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

Description states 'Get load transaction data' which is a specific verb and resource. However, it does not distinguish from sibling tools like get_activity_balances or get_authorizations.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives. Only mentions API limits and suggests narrower filters, but no context on when not to use or which sibling is appropriate.

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