Skip to main content
Glama
Sign In
bitvavo-mcp

bitvavo-mcp

by aderik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_markets

Lists all trading markets on Bitvavo. Optionally filter by quote currency (e.g., EUR) or market status for targeted results.

Instructions

List markets available on Bitvavo. By default only EUR-quoted, trading markets. Pass quote=null or status=null to disable a filter.

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_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
quoteNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the transparency burden. It discloses the non-obvious default filtering behavior and how to disable it. It does not mention output format or error handling, but for a simple list operation, this is adequate and adds value beyond the tool name.

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 two sentences, front-loaded with the primary action, and every clause provides meaningful information. It is concise and well-structured with no wasted 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 simplicity of this listing tool and the absence of an output schema, the description covers the key behavioral aspects: what it lists and how to modify the default filters. The lack of return structure detail is acceptable for this use case.

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 schema provides no descriptions and 0% coverage, so the description must compensate. It explains that quote and status are filters and that null disables them, which adds meaning beyond the bare schema. The implied default values (EUR and trading) are also conveyed, though not explicitly stated as parameter defaults.

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 tool lists markets available on Bitvavo, using the specific verb 'List' and a distinct resource. It also notes the default filter behavior, which further clarifies its scope and differentiates it from sibling tools like get_ticker or get_candles.

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 provides clear context on default behavior (EUR-quoted, trading markets) and explains how to adjust filters by passing null. While it does not explicitly reference alternatives, no sibling tool performs this exact function, so the guidance is sufficient for usage.

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