Skip to main content
Glama

Bitstamp

by io.github.pipeworx-io

Eur Usd

eur_usd
Read-onlyIdempotent

Bitstamp's own EUR↔USD conversion rate — the buy/sell prices Bitstamp applies when converting fiat balances on the exchange, quoted with the exchange's retail markup (the two legs can differ by several percent). Use when you need the rate a Bitstamp account actually transacts at. For the market FX rate — "EURUSD spot", "current euro to dollar rate", anything macro or reporting-grade — use ecb_exchange_rate, which publishes the official euro reference rate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
buyNoEUR/USD buy rate
midNo
noteNo
pairNo
sellNoEUR/USD sell rate
sourceNo
spread_pctNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed7 schema fields changed
    • changedOutput schema / properties / buy / type
      Previous value: -"string"New value: +"number"
    • addedOutput schema / properties / mid
      Added value: +{
+  "type": "number"
+}
    • addedOutput schema / properties / note
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / pair
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / properties / sell / type
      Previous value: -"string"New value: +"number"
    • addedOutput schema / properties / source
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / spread_pct
      Added value: +{
+  "type": "number"
+}
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "buy": {
+      "description": "EUR/USD buy rate",
+      "type": "string"
+    },
+    "sell": {
+      "description": "EUR/USD sell rate",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare read-only and non-destructive, but the description adds critical context: the rate includes retail markup and the two legs can differ by several percent. This explains the behavioral nuance beyond the schema and annotations.

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 sentences: first defines the tool specifically, second gives usage guidance and alternative. Front-loaded and every sentence earns its place. No redundancy.

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?

For a zero-parameter tool with an output schema, the description covers what it is, when to use it, and how it differs from the alternative. No required information is missing.

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 has zero parameters, so schema coverage is trivially 100%. Per the rubric, 0 params baseline is 4. The description adds no parameter-specific information, but none is needed.

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 identifies Bitstamp's own EUR↔USD conversion rate with retail markup, and explicitly distinguishes it from the ECB reference rate. It states the resource (Bitstamp fiat conversion) and the scope (buy/sell prices with markup).

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?

Provides explicit usage guidance: 'Use when you need the rate a Bitstamp account actually transacts at' and for alternatives, 'For the market FX rate... use ecb_exchange_rate'. This directly addresses when to choose this tool over the sibling.

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

All Bitstamp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation2/5

Several tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route questions, while the polymarket_edges, polymarket_arbitrage, and related tools blur edge-detection boundaries. The server's Bitstamp identity also clashes with the bulk of tools being unrelated data-research, making selection harder.

Naming Consistency3/5

Tool names are all lowercase snake_case, which is consistent formatting, but no coherent verb_noun pattern emerges. Some are verb-first (ask_pipeworx, compare_entities, discover_tools) while others are noun-first or resource-based (ticker_hour, order_book, polymarket_edges), and the naming style differs across the two major domains.

Tool Count2/5

At 38 tools, the set is well over the 15-tool threshold for a focused server, and the majority of tools are unrelated to the server's Bitstamp name. The count feels bloated and scattershot—it would be better split into separate data-research and exchange servers.

Completeness3/5

The data-research and question-answering surface is broadly covered, with meta-tools and validation. However, the Bitstamp exchange half is incomplete: it only provides public market data (ticker, order book, trades, OHLC) with no trading, account, or private-data operations, an obvious gap given the server's name.

Resources