Skip to main content
Glama

BlockVectra Docs

by com.blockvectra
OverviewDiscussionsAdmin

List Supported Chains

list_chains
Read-only

Fetch supported blockchain networks and static parameters from GET /v1/chains. methods.allow and methods.deny support wildcard patterns where deny takes precedence over allow. state_window_blocks indicates the historical state window in blocks for state queries (null when full history is available); max_logs_block_range limits log queries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties
      Removed value: -{}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "chains": {
+      "items": {
+        "properties": {
+          "chain": {
+            "type": "string"
+          },
+          "chain_id": {
+            "type": "number"
+          },
+          "data": {
+            "type": "boolean"
+          },
+          "jsonrpc": {
+            "type": "boolean"
+          },
+          "max_logs_block_range": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "methods": {
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "name": {
+            "type": "string"
+          },
+          "state_window_blocks": {
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "chain"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "chains"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A3.9/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 real behavioral context beyond that: deny takes precedence over allow when matching wildcards, and a null state_window_blocks means full history is available. It does not discuss caching/freshness of this static data, which is the only notable gap.

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?

A compact paragraph, front-loaded with the operation and endpoint, followed by field semantics. It is efficient, though the trailing field explanations partly duplicate information an output schema already conveys.

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 a parameterless, read-only lookup with an output schema, the description is sufficient: it establishes purpose, endpoint, and the interpretation of the trickier returned fields. The only missing element is guidance on when this lookup is needed relative to the other API tools.

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 input parameters, so per the rubric the baseline is 4. The description appropriately spends its space on the semantics of the returned fields instead, and the schema requires no compensating explanation.

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?

The description names a concrete verb and resource ('Fetch supported blockchain networks and static parameters') and pins the exact endpoint (GET /v1/chains), so the agent knows precisely what this returns. The 'chains' resource is clearly distinct from the sibling tools, which cover pricing, status, usage estimation, and documentation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no statement of when to call this versus the siblings (get_pricing, get_status, estimate_usage, etc.) and no prerequisites or ordering guidance. The intended use - retrieving static per-chain configuration - must be inferred entirely from the field names.

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

All BlockVectra Docs 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