Skip to main content
Glama

Bitview

by io.github.bitcoinresearchkit
OverviewDiscussionsAdmin

Transaction first-seen times

get_transaction_times
Read-onlyIdempotent

First-seen UNIX timestamps in seconds, in request order, of transactions in the mempool or that recently left it other than by replacement (mined ones included); 0 otherwise.

Mempool.space docs

REST operation: GET /api/v1/transaction-times.

Input Schema

NameRequiredDescriptionDefault
txidsYesTransaction IDs to look up (max 100 per request).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • changedInput schema / $defs / Txid / description
      Previous value: -"Transaction ID (hash)"New value: +"A transaction ID: its hash."
    • addedInput schema / $defs / Txid / pattern
      Added value: +"^[0-9a-f]{64}$"
    • removedInput schema / properties / txId[]
      Removed value: -{
-  "description": "Transaction IDs to look up (max 250 per request).",
-  "items": {
-    "$ref": "#/$defs/Txid"
-  },
-  "type": "array"
-}
    • addedInput schema / properties / txids
      Added value: +{
+  "description": "Transaction IDs to look up (max 100 per request).",
+  "items": {
+    "$ref": "#/$defs/Txid"
+  },
+  "maxItems": 100,
+  "minItems": 1,
+  "type": "array"
+}
    • changedInput schema / required
      Previous value: -[
-  "txId[]"
-]New value: +[
+  "txids"
+]
    • addedOutput schema / $defs
      Added value: +{
+  "Timestamp": {
+    "minimum": 0,
+    "type": "integer"
+  }
+}
    • addedOutput schema / items / $ref
      Added value: +"#/$defs/Timestamp"
    • removedOutput schema / items / format
      Removed value: -"uint64"
    • removedOutput schema / items / minimum
      Removed value: -0
    • removedOutput schema / items / type
      Removed value: -"integer"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses important behavior: timestamps are UNIX seconds, results follow request order, mined transactions are included, replacement transactions are excluded, and the fallback value is 0. This is substantive context for interpreting output, though error and freshness semantics are not 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 front-loaded with the return semantics and edge cases, then supplies a docs link and REST operation. Every sentence is compact and useful, with no filler.

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 simple read-only lookup with a fully described input schema, complete annotations, and an output schema, the description supplies sufficient behavioral context. The key edge cases and ordering semantics are explained, so an agent can invoke and interpret the tool correctly.

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%, and the single txids parameter is fully documented in the schema. The description adds slightly by saying values are returned 'in request order', but it does not otherwise add parameter meaning beyond the schema; baseline 3 is appropriate.

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?

The description states a specific verb and resource: it returns first-seen UNIX timestamps for requested transactions. 'First-seen' and the mempool/recently-left scope distinguish it from general transaction lookups like get_tx or get_tx_status, though it does not explicitly name those siblings.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The description explains the data scope but leaves the agent to infer when this tool is preferable to get_tx_status or other transaction tools.

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

All Bitview 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