Skip to main content
Glama
BlockRunAI

BlockRun MCP

Official
by BlockRunAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

blockrun_rpc

Destructive

Execute raw JSON-RPC calls against 40+ blockchains via a single endpoint, no node or API key needed. Use for contract reads, balances, blocks, logs, gas, or any chain-native method with per-call pricing and batch support.

Instructions

Raw JSON-RPC against 40+ blockchains — one endpoint, no node, no API key. $0.002 base per call plus the gateway's flat tx fee ($0.001 today; we reserve $0.002, so budget/confirm show $0.004 per single call). A JSON-RPC batch charges $0.002 per element plus ONE fee — batch when you can.

Use when you need data the higher-level tools don't cover: contract reads (eth_call), balances, blocks, txs, logs, gas, or any chain-native RPC method.

Networks (full catalog in the rpc skill): ethereum, base, arbitrum, optimism, polygon, bsc, avalanche, solana, bitcoin, sui, near, ripple, polkadot, dogecoin, litecoin, monad, berachain, unichain, hyperevm, sonic, and 20+ more.

Examples: blockrun_rpc({ network: "ethereum", method: "eth_blockNumber" }) blockrun_rpc({ network: "base", method: "eth_getBalance", params: ["0xabc...", "latest"] }) blockrun_rpc({ network: "solana", method: "getSlot" }) blockrun_rpc({ network: "bitcoin", method: "getblockchaininfo" }) blockrun_rpc({ network: "ethereum", body: [{jsonrpc:"2.0",id:1,method:"eth_blockNumber"},{...}] }) // batch

Prefer blockrun_price (free quotes) or blockrun_dex (free DEX data) when they cover the question — this tool is for raw chain access.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoFull JSON-RPC 2.0 body or an array of them (batch). Overrides method/params when set.
methodNoJSON-RPC method, e.g. 'eth_blockNumber', 'eth_call', 'getSlot' (Solana), 'getblockchaininfo' (Bitcoin). Required unless 'body' is set.
paramsNoJSON-RPC params array for the method, e.g. ['0xabc...', 'latest'].
networkYesChain key, e.g. 'ethereum', 'base', 'solana', 'bitcoin', 'arbitrum', 'polygon'. Unknown slugs pass through to the Tatum gateway.
agent_idNoAgent identifier for budget tracking and enforcement.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.45.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Addedv0.22.0

TDQS

A4.3/5.0
Behavior4/5

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

Adds meaningful behavior beyond annotations: no node required, no API key, per-call cost, flat fee, batch pricing, and network slug pass-through. The destructiveHint annotation already covers mutation risk, so the description needn't restate it.

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?

Well structured with a clear opening, usage guidance, network overview, examples, and priority note. The pricing details and example list are useful but slightly longer than strictly necessary; each section earns its place.

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?

Complete enough for a raw JSON-RPC tool: covers purpose, when to use, cost, network list, and example calls including batches. Lacks explicit note about output/error shape and broader write-method safety, but the standard JSON-RPC response format is inferable.

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 coverage is 100%, so the schema already documents method, params, body, network, and agent_id. The description adds examples and clarifies body/method override behavior, but doesn't substantially extend the parameter semantics beyond what's structured.

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 action and resource: raw JSON-RPC access across 40+ chains. It differentiates itself from the higher-level tools and provides concrete examples, making the tool's purpose immediately clear.

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?

Explicitly says to use this tool when higher-level tools don't cover the need, and names alternatives (blockrun_price, blockrun_dex) to prefer when they do. Also gives practical guidance on when to use batch requests.

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

Deploy Server

Other Tools