Skip to main content
Glama

BlockVectra: multi-chain RPC & Data API

by com.blockvectra
OverviewDiscussionsAdmin

List Documentation Pages

list_docs
Read-only

List all available documentation pages, relative paths, and titles from the static documentation index, including webhook push subscriptions, signatures, delivery and billing. Available without an API key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoPublished documentation language (case-insensitive, e.g. zh-hant or zh-Hant). Omit for English; unavailable languages return an error.

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": {
+          "count": {
+            "type": "number"
+          },
+          "docs": {
+            "items": {
+              "properties": {
+                "path": {
+                  "type": "string"
+                },
+                "summary": {
+                  "type": "string"
+                },
+                "title": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "title",
+                "path",
+                "summary"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "lang": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "lang",
+          "count",
+          "docs"
+        ],
+        "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"
-  },
-  "docs": {
-    "items": {
-      "properties": {
-        "path": {
-          "type": "string"
-        },
-        "summary": {
-          "type": "string"
-        },
-        "title": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "title",
-        "path",
-        "summary"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "lang": {
-    "type": "string"
-  }
-}
    • removedOutput schema / required
      Removed value: -[
-  "lang",
-  "count",
-  "docs"
-]
  2. Changed1 schema field changed
    • changedInput schema / properties / lang / description
      Previous value: -"Published documentation language. Omit for English; unavailable languages return an error."New value: +"Published documentation language (case-insensitive, e.g. zh-hant or zh-Hant). Omit for English; unavailable languages return an error."
  3. Changed1 schema field changed
    • changedInput schema / properties / lang / enum
      Previous value: -[
-  "en",
-  "zh",
-  "de",
-  "es",
-  "fr",
-  "id",
-  "ja",
-  "ko",
-  "pt-br",
-  "ru",
-  "tr",
-  "vi",
-  "zh-hant"
-]New value: +[
+  "en",
+  "zh",
+  "de",
+  "es",
+  "fr",
+  "id",
+  "ja",
+  "ko",
+  "pt-br",
+  "ru",
+  "th",
+  "tr",
+  "uk",
+  "vi",
+  "zh-hant"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / lang / enum
      Previous value: -[
-  "en",
-  "zh",
-  "es",
-  "id",
-  "ja",
-  "ko",
-  "pt-br",
-  "ru",
-  "vi",
-  "zh-hant"
-]New value: +[
+  "en",
+  "zh",
+  "de",
+  "es",
+  "fr",
+  "id",
+  "ja",
+  "ko",
+  "pt-br",
+  "ru",
+  "tr",
+  "vi",
+  "zh-hant"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / lang / enum
      Previous value: -[
-  "en",
-  "zh",
-  "es",
-  "id",
-  "ja",
-  "ko",
-  "pt-br",
-  "vi",
-  "zh-hant"
-]New value: +[
+  "en",
+  "zh",
+  "es",
+  "id",
+  "ja",
+  "ko",
+  "pt-br",
+  "ru",
+  "vi",
+  "zh-hant"
+]
  6. Changed1 schema field changed
    • changedInput schema / properties / lang / enum
      Previous value: -[
-  "en",
-  "zh",
-  "ja",
-  "ko",
-  "pt-br"
-]New value: +[
+  "en",
+  "zh",
+  "es",
+  "id",
+  "ja",
+  "ko",
+  "pt-br",
+  "vi",
+  "zh-hant"
+]
  7. Changed1 schema field changed
    • changedInput schema / properties / lang / enum
      Previous value: -[
-  "en",
-  "zh",
-  "ko"
-]New value: +[
+  "en",
+  "zh",
+  "ja",
+  "ko",
+  "pt-br"
+]
  8. Changed1 schema field changed
    • changedInput schema / properties / lang / enum
      Previous value: -[
-  "en",
-  "zh"
-]New value: +[
+  "en",
+  "zh",
+  "ko"
+]
  9. Changed1 schema field changed
    • changedInput schema / properties / lang / description
      Previous value: -"Documentation language: 'en' for English or 'zh' for Chinese. Defaults to 'en'."New value: +"Published documentation language. Omit for English; unavailable languages return an error."
  10. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: the source is a 'static documentation index' (fixed, not live) and access requires no API key — both operationally useful facts.

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?

One sentence, front-loaded with the core action and result shape. The trailing 'including webhook push subscriptions, signatures, delivery and billing' is a somewhat odd topical enumeration but not enough to count as waste.

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?

An output schema exists, so return-value explanation is unnecessary. The definition covers what is listed, where it comes from, and the auth posture — sufficient for an agent to call it 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 optional lang param is fully documented in-schema (case-insensitive, omit for English, error on unavailable languages). The description adds no parameter detail, 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 (List) and resource (documentation pages), and goes further to name the payload — relative paths and titles — from the static documentation index. It is distinguishable from read_doc and search_docs in spirit, though it never explicitly contrasts itself with 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Conveys implied usage as a discovery/index tool and notes the useful constraint 'Available without an API key,' but gives no explicit when-to-use or when-not-to-use guidance relative to read_doc or search_docs.

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