Skip to main content
Glama
BlockRunAI

BlockRun MCP

Official
by BlockRunAI
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

blockrun_wallet

Check USDC balances, fund the wallet, switch payment chains, and set or delegate agent spending limits. Resolve payment or balance errors before running paid operations.

Instructions

Call this tool to manage the BlockRun payment wallet and control agent spending budgets.

Call this FIRST if any other blockrun_* tool returns a payment/balance error. Call this to check your current USDC balance before expensive operations. Call this to set spending limits before spawning child agents.

The server holds TWO wallets — one on Base, one on Solana — but pays on ONE active chain at a time. status shows both addresses/balances and which is active. Default chain is Base.

To pay on Solana (no env vars, no file editing, no restart):

  1. action:"chain" chain:"solana" → provisions + activates the Solana wallet

  2. action:"setup" → Solana address + funding QR (send USDC SPL on Solana) Switch back with action:"chain" chain:"base". Base-only — these ignore Solana and need Base: blockrun_music, blockrun_speech, blockrun_realface, paid blockrun_price, blockrun_chat routing:"smart", and native Anthropic (claude-*). blockrun_image and blockrun_video pay on either chain.

Actions:

  • status (default): Both wallet addresses + USDC balances, active chain, session spending

  • deposit: Buy USDC with a card — mints a one-time Coinbase Onramp link and opens it in the browser (Base only; funds settle into your own wallet). Paid tools auto-open this on an out-of-funds failure; call it directly to fund up front.

  • setup: Get funding instructions + QR code for the ACTIVE chain (call this when balance is 0)

  • qr: Open QR code (active chain) in system viewer

  • chain + chain:"base"|"solana": Switch the active payment chain (omit chain: to just see the current one)

Budget controls:

  • budget + budget_action:"set" + budget_amount:1.00 → Set global spend cap

  • budget + budget_action:"clear" → Remove global spend cap

Multi-agent orchestration:

  • delegate + agent_id:"research" + agent_limit:2.00 → Allocate $2 to a child agent

  • revoke + agent_id:"research" → Remove a child agent's budget

  • report → See per-agent spending breakdown

Usage pattern for multi-agent systems:

  1. blockrun_wallet action:"delegate" agent_id:"worker-1" agent_limit:1.00

  2. Pass agent_id:"worker-1" to all blockrun_chat/search/etc calls for that agent

  3. blockrun_wallet action:"report" to audit spending

Do NOT call this for actual AI queries — use blockrun_chat for that.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNoTarget chain for action='chain'. Omit to view the current active chain.
actionNoWhat to dostatus
agent_idNoAgent identifier for delegate/revoke/report actions
agent_limitNoBudget limit in USD for this agent (required for delegate action)
budget_actionNoBudget action (for action='budget')
budget_amountNoBudget limit in USD (for budget_action='set')

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.45.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed1 schema field changedv0.31.6
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "status",
-  "setup",
-  "qr",
-  "chain",
-  "budget",
-  "delegate",
-  "revoke",
-  "report"
-]New value: +[
+  "status",
+  "deposit",
+  "setup",
+  "qr",
+  "chain",
+  "budget",
+  "delegate",
+  "revoke",
+  "report"
+]
  3. First observedv0.16.2

TDQS

A5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses significant behavioral side effects: deposit 'mints a one-time Coinbase Onramp link and opens it in the browser,' chain switch 'provisions + activates the Solana wallet,' and budget/delegate/revoke actions modify spending state. It also reveals the two-wallet architecture and active-chain behavior that annotations cannot express.

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?

The description is long but highly structured with clear section headers (Actions, Budget controls, Multi-agent orchestration, Usage pattern) and front-loaded critical guidance in the first three sentences. Every section earns its place given the tool's 9 actions, 6 parameters, and multi-chain behavior. The formatting makes it scannable despite its length.

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?

No output schema exists, but the description compensates by describing what status reports ('both addresses/balances and which is active' and 'session spending'). It covers the full action matrix, cross-chain provisioning steps, Base-only restrictions for sibling tools, budget controls, multi-agent delegation, and the recommended usage pattern. Nothing an agent needs to correctly invoke this tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema already documents all 6 parameters (100% coverage), the description adds substantial meaning: it explains each action value with usage examples (e.g., 'chain + chain:"base"|"solana" → Switch the active payment chain'), clarifies defaults ('status (default)'), states that agent_limit is required for delegate, and describes the effect of omitting chain ('omit chain: to just see the current one'). This goes well beyond the schema's terse 'What to do'.

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?

Description opens with a specific verb and resource: 'manage the BlockRun payment wallet and control agent spending budgets.' It distinguishes itself from the 19 sibling blockrun_* tools by immediately stating what it is for and ends with an explicit exclusion: 'Do NOT call this for actual AI queries — use blockrun_chat for that.' This leaves no ambiguity about its purpose relative to siblings.

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?

The description gives concrete when-to-use rules: call first on payment/balance errors, before expensive operations, and before spawning child agents. It also names alternatives and exclusions ('Base-only... need Base: blockrun_music...' and 'use blockrun_chat for that'), making the routing decision explicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BlockRunAI/blockrun-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server