Skip to main content
Glama

BlockVectra: multi-chain RPC & Data API

by com.blockvectra
OverviewDiscussionsAdmin

Get Service and Network Status

get_status
Read-only

Live operational status and network health from GET /v1/status. Confirm chain status is 'ok' before calling methods; see list_chains for static chain capabilities and method policies. For Data API, data_status can be 'ok', 'syncing' (queryable and billed normally, but indexing is lagging behind latest block time), or 'unavailable'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / anyOf
      Added value: +[
+  {
+    "allOf": [
+      {
+        "properties": {
+          "chains": {
+            "type": "array"
+          },
+          "checked_at": {
+            "type": "string"
+          },
+          "gateway": {
+            "type": "object"
+          }
+        },
+        "required": [
+          "checked_at",
+          "gateway",
+          "chains"
+        ],
+        "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: -{
-  "chains": {
-    "type": "array"
-  },
-  "checked_at": {
-    "type": "string"
-  },
-  "gateway": {
-    "type": "object"
-  }
-}
    • removedOutput schema / required
      Removed value: -[
-  "checked_at",
-  "gateway",
-  "chains"
-]
  2. Changed1 schema field changed
    • changedOutput schema / required
      Previous value: -[
-  "gateway",
-  "chains"
-]New value: +[
+  "checked_at",
+  "gateway",
+  "chains"
+]
  3. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties
      Removed value: -{}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "chains": {
+      "type": "array"
+    },
+    "checked_at": {
+      "type": "string"
+    },
+    "gateway": {
+      "type": "object"
+    }
+  },
+  "required": [
+    "gateway",
+    "chains"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds real behavioral context beyond them — a gating prerequisite for other calls and the fact that 'syncing' is still queryable and billed normally while indexing lags. That billing/lag nuance is not derivable from the schema or annotations. It stops short of stating auth needs or freshness/refresh cadence, keeping it just under the top mark.

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?

Purpose is front-loaded, followed by the usage rule and then status-value semantics — a sensible order with no filler sentences. The final clause is dense and packs several state definitions plus a billing implication into one sentence, which slightly taxes readability.

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 read tool with an output schema and readOnly annotations, the description supplies everything an agent needs: what it returns at a high level, when to call it, and what the returned status values mean. Nothing material 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 takes zero parameters, so per the rubric the baseline is 4; there is no parameter surface for the description to explain. The description correctly adds no parameter noise.

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+resource — 'live operational status and network health' — and anchors it to the concrete endpoint GET /v1/status. It explicitly distinguishes itself from list_chains ('static chain capabilities and method policies'), so an agent can separate the two without opening schemas.

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?

Gives an explicit precondition ('Confirm chain status is ok before calling methods') and routes the agent to the correct alternative ('see list_chains for static chain capabilities and method policies'). Both when-to-use and when-to-use-something-else are covered.

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