BlockVectra: multi-chain RPC & Data API

Query Data API

data_api_get

Read-only

Query the BlockVectra Data API for a specified chain and path using your BlockVectra API key. For endpoint schemas and parameter specifications, see the OpenAPI contract at https://docs.blockvectra.com/openapi/data.yaml. Requires the 'x-api-key' or 'Authorization: Bearer ' HTTP header in your MCP client configuration (keys must not be passed in tool parameters or chat). Returns the HTTP status and JSON response body.

Input Schema

TableJSON Schema

Name	Required	Description
`path`	Yes	Path after '/v1/data/{chain}/' (e.g. 'status/freshness', 'address/0x.../balances'). Must not start with '/', and cannot contain '..', '//', '?', '#', or '%'.
`chain`	Yes	Target blockchain network slug (e.g. 'robinhood_mainnet').
`query`	No	Optional URL query parameters as key-value pairs.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 18, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "allOf": [
-      {
-        "properties": {
-          "_truncated": {
-            "type": "boolean"
-          },
-          "balance_units": {
-            "description": "Remaining balance units after this request (only present when balance is known and x-bv-meter: 1 was sent).",
-            "type": "integer"
-          },
-          "bytes": {
-            "type": "integer"
-          },
-          "cu_charged": {
-            "description": "Compute Units billed for this request (only present when charged and x-bv-meter: 1 was sent).",
-            "type": "integer"
-          },
-          "data": {},
-          "error": {
-            "type": "string"
-          },
-          "status": {
-            "type": "number"
-          }
-        },
-        "type": "object"
-      },
-      {
-        "not": {
-          "properties": {
-            "error": {
-              "const": "invalid_tool_arguments",
-              "type": "string"
-            }
-          },
-          "required": [
-            "error"
-          ],
-          "type": "object"
-        }
-      }
-    ]
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "error": {
-        "const": "invalid_tool_arguments",
-        "type": "string"
-      },
-      "message": {
-        "minLength": 1,
-        "type": "string"
-      },
-      "reason": {
-        "enum": [
-          "invalid_root",
-          "schema_type",
-          "schema_enum",
-          "undeclared_property",
-          "credential_field",
-          "credential_value"
-        ],
-        "type": "string"
-      }
-    },
-    "required": [
-      "error",
-      "reason",
-      "message"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "allOf": [
+      {
+        "anyOf": [
+          {
+            "allOf": [
+              {
+                "properties": {
+                  "_truncated": {
+                    "type": "boolean"
+                  },
+                  "balance_units": {
+                    "description": "Remaining balance units after this request (only present when balance is known and x-bv-meter: 1 was sent).",
+                    "type": "integer"
+                  },
+                  "bytes": {
+                    "type": "integer"
+                  },
+                  "cu_charged": {
+                    "description": "Compute Units billed for this request (only present when charged and x-bv-meter: 1 was sent).",
+                    "type": "integer"
+                  },
+                  "data": {},
+                  "error": {
+                    "type": "string"
+                  },
+                  "status": {
+                    "type": "number"
+                  }
+                },
+                "type": "object"
+              },
+              {
+                "not": {
+                  "properties": {
+                    "error": {
+                      "const": "executor_request_rejected",
+                      "type": "string"
+                    }
+                  },
+                  "required": [
+                    "error"
+                  ],
+                  "type": "object"
+                }
+              }
+            ]
+          },
+          {
+            "additionalProperties": false,
+            "properties": {
+              "error": {
+                "const": "executor_request_rejected",
+                "type": "string"
+              },
+              "message": {
+                "minLength": 1,
+                "type": "string"
+              },
+              "reason": {
+                "enum": [
+                  "chain_invalid",
+                  "path_invalid"
+                ],
+                "type": "string"
+              }
+            },
+            "required": [
+              "error",
+              "reason",
+              "message"
+            ],
+            "type": "object"
+          }
+        ],
+        "type": "object"
+      },
+      {
+        "not": {
+          "properties": {
+            "error": {
+              "const": "invalid_tool_arguments",
+              "type": "string"
+            }
+          },
+          "required": [
+            "error"
+          ],
+          "type": "object"
+        }
+      }
+    ]
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "error": {
+        "const": "invalid_tool_arguments",
+        "type": "string"
+      },
+      "message": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "reason": {
+        "enum": [
+          "invalid_root",
+          "schema_type",
+          "schema_enum",
+          "undeclared_property",
+          "credential_field",
+          "credential_value"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "error",
+      "reason",
+      "message"
+    ],
+    "type": "object"
+  }
+]

Changed2 schema fields changedOct 18, 2026

addedOutput schema / anyOf

Added value: +[
+  {
+    "allOf": [
+      {
+        "properties": {
+          "_truncated": {
+            "type": "boolean"
+          },
+          "balance_units": {
+            "description": "Remaining balance units after this request (only present when balance is known and x-bv-meter: 1 was sent).",
+            "type": "integer"
+          },
+          "bytes": {
+            "type": "integer"
+          },
+          "cu_charged": {
+            "description": "Compute Units billed for this request (only present when charged and x-bv-meter: 1 was sent).",
+            "type": "integer"
+          },
+          "data": {},
+          "error": {
+            "type": "string"
+          },
+          "status": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      {
+        "not": {
+          "properties": {
+            "error": {
+              "const": "invalid_tool_arguments",
+              "type": "string"
+            }
+          },
+          "required": [
+            "error"
+          ],
+          "type": "object"
+        }
+      }
+    ]
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "error": {
+        "const": "invalid_tool_arguments",
+        "type": "string"
+      },
+      "message": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "reason": {
+        "enum": [
+          "invalid_root",
+          "schema_type",
+          "schema_enum",
+          "undeclared_property",
+          "credential_field",
+          "credential_value"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "error",
+      "reason",
+      "message"
+    ],
+    "type": "object"
+  }
+]

removedOutput schema / properties

Removed value: -{
-  "_truncated": {
-    "type": "boolean"
-  },
-  "balance_units": {
-    "description": "Remaining balance units after this request (only present when balance is known and x-bv-meter: 1 was sent).",
-    "type": "integer"
-  },
-  "bytes": {
-    "type": "integer"
-  },
-  "cu_charged": {
-    "description": "Compute Units billed for this request (only present when charged and x-bv-meter: 1 was sent).",
-    "type": "integer"
-  },
-  "data": {},
-  "error": {
-    "type": "string"
-  },
-  "status": {
-    "type": "number"
-  }
-}

Changed4 schema fields changedOct 2, 2026
- addedOutput schema / properties / _truncated
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / bytes
```
Added value: +{
+  "type": "integer"
+}
```
- addedOutput schema / properties / error
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / required
```
Removed value: -[
-  "status",
-  "data"
-]
```

Changed2 schema fields changedOct 2, 2026

addedOutput schema / properties / balance_units

Added value: +{
+  "description": "Remaining balance units after this request (only present when balance is known and x-bv-meter: 1 was sent).",
+  "type": "integer"
+}

addedOutput schema / properties / cu_charged

Added value: +{
+  "description": "Compute Units billed for this request (only present when charged and x-bv-meter: 1 was sent).",
+  "type": "integer"
+}

AddedOct 1, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered, but the description adds genuinely useful context beyond them: the required auth header ('x-api-key' or Bearer), the warning that keys must not be passed as tool parameters or in chat, and the return shape (HTTP status plus JSON body). It omits rate limits and error behavior, keeping it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences that front-load the purpose, then auth, then return value, with no filler. Slightly dense but every sentence carries operational information.

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 an open-world API passthrough, the description covers the essentials: what it queries, where the contract lives, how auth is supplied, and what comes back, and an output schema exists so return values need no elaboration. It could be more complete by naming which sibling to use for specific read tasks instead of raw passthrough.

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%, so chain and path are already fully documented and the description adds no syntax beyond them. The OpenAPI pointer routes the agent to endpoint-specific parameters, but that is not meaning for this tool's own 3 parameters, so the baseline 3 applies.

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?

States a specific verb and resource ('Query the BlockVectra Data API') plus the scoping surface (a specified chain and path). It is distinguishable from most siblings, though it never contrasts itself with the closest passthrough sibling, rpc_call.

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?

Usage is implied by the OpenAPI contract pointer ('For endpoint schemas and parameter specifications, see...'), which tells the agent where to look but not when to prefer this tool over rpc_call or the get_* siblings. No explicit when-to-use or when-not guidance is given.

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

All BlockVectra: multi-chain RPC & Data API tools Inspect

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.