Skip to main content
Glama
Sign In
bitvavo-mcp

bitvavo-mcp

by aderik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_transactions

Query locally-stored crypto transaction history from Bitvavo. Filter by currency, type, or date range; returns newest transactions first, defaulting to the most recent 100.

Instructions

Query the locally-stored transaction history (populated via import_transactions). Newest first. Without filters returns the most recent 100 rows. Combine currency + type to narrow.

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": "get_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
typeNo
limitNo
currencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description discloses important behavioral context: data is locally stored, populated via import_transactions, ordered newest first, and limited to 100 rows by default. It also notes that filters narrow results. It does not mention response format or error handling, but the core behaviors are covered.

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?

The description is three concise sentences, front-loaded with the core purpose, then adding ordering/default limit, and finally filter combination advice. Every sentence provides value with no redundancy or filler.

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?

Given the lack of an output schema and annotations, the description should clarify what the returned transaction list contains or how to paginate. It does not describe the response structure or the semantics of from/to, leaving the agent to infer important details for a tool with five parameters.

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

Parameters2/5

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

Schema description coverage is 0%, and the description only mentions currency and type by name with the advice to combine them. It does not explain the meaning of 'from' or 'to', nor the limit parameter beyond the default. The phrase 'Without filters returns the most recent 100 rows' implies limit behavior but lacks concrete detail.

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 uses the specific verb 'Query' and identifies the resource as 'locally-stored transaction history', explicitly noting it is populated via import_transactions. It clearly distinguishes from sibling tools like get_trades or get_withdrawals by focusing on the full transaction history.

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

Usage Guidelines3/5

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

The description gives useful tips like 'Combine currency + type to narrow' and explains the default behavior without filters. However, it does not explicitly state when to use this tool versus alternatives, so usage guidance is implied rather than directly contrasted with siblings.

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

Deploy Server

Other Tools