Skip to main content
Glama

Bitstamp

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Transactions

transactions
Read-onlyIdempotent

Fetch recent Bitstamp trades for a currency pair; optional time filter (minute, hour, day) sets the lookback window. Returns trade id, price, amount, type, and timestamp.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timeNo
currency_pairYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
itemsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / count
      Added value: +{
+  "type": "number"
+}
    • addedOutput schema / properties / items
      Added value: +{
+  "items": {
+    "properties": {
+      "amount": {
+        "type": "string"
+      },
+      "date": {
+        "type": "string"
+      },
+      "price": {
+        "type": "string"
+      },
+      "tid": {
+        "type": "string"
+      },
+      "type": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • removedOutput schema / properties / transactions
      Removed value: -{
-  "description": "List of recent transactions",
-  "items": {
-    "properties": {
-      "amount": {
-        "description": "Transaction amount",
-        "type": "string"
-      },
-      "date": {
-        "description": "Transaction date",
-        "type": "string"
-      },
-      "price": {
-        "description": "Transaction price",
-        "type": "string"
-      },
-      "tid": {
-        "description": "Transaction ID",
-        "type": "string"
-      },
-      "type": {
-        "description": "Buy or sell",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "currency_pair": "btcusd"
+  },
+  {
+    "currency_pair": "ethusd",
+    "time": "hour"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "transactions": {
+      "description": "List of recent transactions",
+      "items": {
+        "properties": {
+          "amount": {
+            "description": "Transaction amount",
+            "type": "string"
+          },
+          "date": {
+            "description": "Transaction date",
+            "type": "string"
+          },
+          "price": {
+            "description": "Transaction price",
+            "type": "string"
+          },
+          "tid": {
+            "description": "Transaction ID",
+            "type": "string"
+          },
+          "type": {
+            "description": "Buy or sell",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds useful context about recency and lookback windows, but does not disclose potential rate limits, pagination, or ordering behavior. With annotations present, this is adequate but not rich.

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?

A single well-structured sentence that leads with the action and resource, then covers the optional parameter and return fields. Every clause earns its place with no redundancy or filler.

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?

For a low-complexity read-only tool with an output schema and rich annotations, the description covers the essential invocation details: required pair, optional time filter, allowed values, and returned fields. The only minor gap is that currency_pair format is not explicitly described, though the schema examples show 'btcusd' style.

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 coverage is 0%, so the description must compensate. It does explain the time parameter's allowed values (minute, hour, day) and its lookback semantics, which adds real value. However, it does not explain the currency_pair format expected beyond the name; the schema examples partially fill that gap.

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?

States a specific action (fetch), a specific resource (recent Bitstamp trades), and the primary parameter (currency pair). The optional time filter and returned fields further clarify what this tool is, distinguishing it from siblings like order_book or ticker.

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 clearly identifies the use case: fetching recent trades for a currency pair, with an optional lookback window. It doesn't explicitly name alternatives or when-not-to-use, but the context is clear enough for an agent to select this tool over ticker/order_book.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources