BlockVectra: multi-chain RPC & Data API

Explain Error Code or Reason

explain_error

Read-only

Lookup error code, reason, or HTTP status in the official error reference catalog. Returns meaning, billing implications (whether the call was billed), retryability, retry delay, recommended agent action, and documentation URL.

Input Schema

TableJSON Schema

Name	Required	Description
`code`	No	Error code (e.g. -32600, -32005, -32020, or console code string like 'siwe_invalid').
`lang`	No	Response language (case-insensitive). Defaults to 'en'.
`reason`	No	Error reason slug (e.g. 'invalid_request', 'key_rate_limit', 'insufficient_balance', 'not_found').
`http_status`	No	HTTP status code (e.g. 200, 400, 402, 404, 429, 500, 503).

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 18, 2026

addedOutput schema / anyOf

Added value: +[
+  {
+    "allOf": [
+      {
+        "properties": {
+          "count": {
+            "type": "number"
+          },
+          "errors": {
+            "items": {
+              "properties": {
+                "action": {
+                  "type": "string"
+                },
+                "billed": {
+                  "type": [
+                    "boolean",
+                    "string"
+                  ]
+                },
+                "category": {
+                  "type": "string"
+                },
+                "code": {
+                  "type": [
+                    "number",
+                    "string"
+                  ]
+                },
+                "docs_url": {
+                  "type": "string"
+                },
+                "http": {
+                  "type": "number"
+                },
+                "message": {
+                  "type": "string"
+                },
+                "reason": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "retry_after": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "retryable": {
+                  "type": "boolean"
+                }
+              },
+              "required": [
+                "code",
+                "http",
+                "message",
+                "billed",
+                "retryable",
+                "action",
+                "docs_url"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "matched": {
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "matched",
+          "errors"
+        ],
+        "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: -{
-  "count": {
-    "type": "number"
-  },
-  "errors": {
-    "items": {
-      "properties": {
-        "action": {
-          "type": "string"
-        },
-        "billed": {
-          "type": [
-            "boolean",
-            "string"
-          ]
-        },
-        "category": {
-          "type": "string"
-        },
-        "code": {
-          "type": [
-            "number",
-            "string"
-          ]
-        },
-        "docs_url": {
-          "type": "string"
-        },
-        "http": {
-          "type": "number"
-        },
-        "message": {
-          "type": "string"
-        },
-        "reason": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "retry_after": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "retryable": {
-          "type": "boolean"
-        }
-      },
-      "required": [
-        "code",
-        "http",
-        "message",
-        "billed",
-        "retryable",
-        "action",
-        "docs_url"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "matched": {
-    "type": "boolean"
-  }
-}

removedOutput schema / required

Removed value: -[
-  "matched",
-  "errors"
-]

Changed1 schema field changedOct 10, 2026

changedInput schema / properties / lang / description

Previous value: -"Response language. Defaults to 'en'."New value: +"Response language (case-insensitive). Defaults to 'en'."

Changed1 schema field changedOct 10, 2026

changedInput schema / properties / lang / enum

Previous value: -[
-  "zh",
-  "en",
-  "ja",
-  "es",
-  "pt-br",
-  "ko",
-  "vi",
-  "zh-hant",
-  "id",
-  "tr",
-  "de",
-  "fr",
-  "ru"
-]New value: +[
+  "zh",
+  "en",
+  "ja",
+  "es",
+  "pt-br",
+  "ko",
+  "vi",
+  "zh-hant",
+  "id",
+  "tr",
+  "de",
+  "fr",
+  "ru",
+  "th",
+  "uk"
+]

Changed2 schema fields changedOct 10, 2026

changedInput schema / properties / lang / description

Previous value: -"Language for explanations: 'en' for English or 'zh' for Chinese. Defaults to 'en'."New value: +"Response language. Defaults to 'en'."

changedInput schema / properties / lang / enum

Previous value: -[
-  "en",
-  "zh"
-]New value: +[
+  "zh",
+  "en",
+  "ja",
+  "es",
+  "pt-br",
+  "ko",
+  "vi",
+  "zh-hant",
+  "id",
+  "tr",
+  "de",
+  "fr",
+  "ru"
+]

AddedSep 30, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds some behavioral value by flagging that the catalog encodes billing implications and retryability, but that is largely return-payload information already covered by the output schema, and it says nothing about auth, rate limits, or what happens when a code is unknown.

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?

Two tight sentences: the first names the lookup target and source, the second front-loads the returned fields as a compact list. No filler, no restatement of the tool name or title's tautology.

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?

An output schema exists, so the description is not obliged to enumerate return fields (though it helpfully does). It is nearly complete for a read-only lookup, with the one gap being guidance on how to combine the four zero-required parameters — an agent is left to guess whether to pass code, reason, or http_status.

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 the baseline is 3. The description's 'error code, reason, or HTTP status' mirrors the schema's documented parameters without adding anything the schema lacks. Notably, it does not clarify that all four parameters are optional or that at least one identifier must be supplied — a real ambiguity given required parameters = 0.

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 (lookup) and a specific resource (error code, reason, or HTTP status in the official error reference catalog), and it enumerates exactly what the lookup returns. None of the sibling tools (search_docs, read_doc, get_status, get_method_info) overlap with this, so an agent can route to it without opening a schema.

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 phrasing — you use it when you have an error code/reason/status to interpret — but there is no explicit when-to-use statement and no mention of alternatives such as search_docs or read_doc, which an agent might plausibly reach for when diagnosing an error. No exclusions or prerequisites are 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.