Skip to main content
Glama

BlockVectra: multi-chain RPC & Data API

by com.blockvectra
OverviewDiscussionsAdmin

Get Account Balance and Limits

get_account
Read-only

Get the API key's own balance, Compute Units (CU), rate limits, and key parameters from GET /v1/account using your BlockVectra API key. Free and unbilled. Requires the 'x-api-key' or 'Authorization: Bearer ' HTTP header in your MCP client configuration (never pass keys in tool parameters or chat). Returns the account's key_id, plan, balance_units, balance_cu, balance_as_of_age_ms, and key limits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / anyOf
      Added value: +[
+  {
+    "allOf": [
+      {
+        "properties": {
+          "_truncated": {
+            "type": "boolean"
+          },
+          "balance_as_of_age_ms": {
+            "type": "integer"
+          },
+          "balance_cu": {
+            "type": "integer"
+          },
+          "balance_units": {
+            "type": "integer"
+          },
+          "bytes": {
+            "type": "integer"
+          },
+          "data": {},
+          "error": {
+            "properties": {
+              "code": {
+                "type": "string"
+              },
+              "data": {
+                "properties": {
+                  "docs_url": {
+                    "type": "string"
+                  },
+                  "reason": {
+                    "type": "string"
+                  },
+                  "request_id": {
+                    "type": "string"
+                  },
+                  "retryable": {
+                    "type": "boolean"
+                  }
+                },
+                "type": "object"
+              },
+              "message": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "code",
+              "message"
+            ],
+            "type": [
+              "string",
+              "object"
+            ]
+          },
+          "key": {
+            "properties": {
+              "burst_cu": {
+                "type": "integer"
+              },
+              "cu_cap": {
+                "type": [
+                  "integer",
+                  "null"
+                ]
+              },
+              "cu_cap_remaining": {
+                "type": [
+                  "integer",
+                  "null"
+                ]
+              },
+              "cu_per_sec": {
+                "type": "integer"
+              },
+              "expires_at": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "type": "object"
+          },
+          "key_id": {
+            "type": "string"
+          },
+          "plan": {
+            "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_as_of_age_ms": {
-    "type": "integer"
-  },
-  "balance_cu": {
-    "type": "integer"
-  },
-  "balance_units": {
-    "type": "integer"
-  },
-  "bytes": {
-    "type": "integer"
-  },
-  "data": {},
-  "error": {
-    "properties": {
-      "code": {
-        "type": "string"
-      },
-      "data": {
-        "properties": {
-          "docs_url": {
-            "type": "string"
-          },
-          "reason": {
-            "type": "string"
-          },
-          "request_id": {
-            "type": "string"
-          },
-          "retryable": {
-            "type": "boolean"
-          }
-        },
-        "type": "object"
-      },
-      "message": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "code",
-      "message"
-    ],
-    "type": [
-      "string",
-      "object"
-    ]
-  },
-  "key": {
-    "properties": {
-      "burst_cu": {
-        "type": "integer"
-      },
-      "cu_cap": {
-        "type": [
-          "integer",
-          "null"
-        ]
-      },
-      "cu_cap_remaining": {
-        "type": [
-          "integer",
-          "null"
-        ]
-      },
-      "cu_per_sec": {
-        "type": "integer"
-      },
-      "expires_at": {
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "type": "object"
-  },
-  "key_id": {
-    "type": "string"
-  },
-  "plan": {
-    "type": "string"
-  },
-  "status": {
-    "type": "number"
-  }
-}
  2. Changed3 schema fields changed
    • addedOutput schema / properties / error / properties
      Added value: +{
+  "code": {
+    "type": "string"
+  },
+  "data": {
+    "properties": {
+      "docs_url": {
+        "type": "string"
+      },
+      "reason": {
+        "type": "string"
+      },
+      "request_id": {
+        "type": "string"
+      },
+      "retryable": {
+        "type": "boolean"
+      }
+    },
+    "type": "object"
+  },
+  "message": {
+    "type": "string"
+  }
+}
    • addedOutput schema / properties / error / required
      Added value: +[
+  "code",
+  "message"
+]
    • changedOutput schema / properties / error / type
      Previous value: -"string"New value: +[
+  "string",
+  "object"
+]
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations by disclosing the auth mechanism ('x-api-key' or 'Authorization: Bearer <key>' in client config, never in tool parameters), the billing behavior (free/unbilled), and the data surface returned. The explicit warning against passing keys in parameters is exactly the kind of non-obvious operational context an agent needs.

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 sentences, front-loaded with purpose and endpoint, followed by billing and auth constraints. Dense but each sentence carries distinct information; the trailing enumeration of return fields is the only slightly padded element.

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?

Auth requirements, cost behavior, and scope are all covered, and an output schema already exists so return values need no elaboration (the field list is a redundant but harmless bonus). An agent has everything needed to invoke this correctly.

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 takes zero parameters, so there is nothing for the description to disambiguate beyond what the schema already states. Baseline of 4 applies for a no-parameter tool with 100% schema coverage.

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 verb and resource ('Get the API key's own balance, CU, rate limits, and key parameters') and pins it to an exact endpoint (GET /v1/account). This clearly separates it from siblings like estimate_usage, get_pricing, and get_status, which cover related but distinct concerns.

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?

Provides meaningful selection context by noting the call is 'Free and unbilled,' which tells an agent it can call this without cost concern, unlike usage-estimating or RPC tools. It stops short of explicitly naming an alternative or stating when-not-to-use it, so it does not reach the top of the scale.

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