Skip to main content
Glama

Read Solana JSON-RPC mainnet methods with fallback

rpc_solana
Read-only

Read-only JSON-RPC pass-through for Solana mainnet. Allowed methods: getAccountInfo, getBalance, getTransaction, getSignaturesForAddress (limit <= 100), getTokenAccountsByOwner, getTokenSupply, getSlot, getBlockTime, getLatestBlockhash, getMultipleAccounts (<= 20). Write methods and getProgramAccounts refused. Related tools on this server, for a different need: rpc_evm when you need to read multi-chain EVM JSON-RPC with fallback. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "method": "<method>"
    },
    "name": "rpc_solana"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodYesSolana JSON-RPC read method (e.g. getSlot, getBalance)
paramsNoJSON-RPC parameters array

Output Schema

NameRequiredDescriptionDefault
sourceNo
providerNo
responseNo
checkedAtNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, and the description is consistent, adding substantial context beyond them: the method whitelist, hard caps (limit <= 100, <= 20 accounts), refusal of write methods and getProgramAccounts, and billing semantics ($0.002 per successful call, failed calls not charged). Pricing and failure-charge behavior are things annotations cannot express and are critical for an agent deciding whether to retry.

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?

Front-loaded with scope, then constraints, then routing, then price; the ordering is deliberate and no sentence is filler. The method enumeration is long but necessary given the schema has no enum, and the pricing clause is dense though slightly tacked-on.

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 values need not be explained, and the description covers everything else an agent needs: allowed calls, hard limits, refusals, cost, and the sibling alternative. Nothing required to invoke it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning the schema lacks: the schema accepts any string for 'method' with no enum, and the description supplies the valid value set plus parameter-level limits (limit <= 100, <= 20 accounts). It stops short of explaining the params array shape or per-method parameter differences.

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 and resource ('Read-only JSON-RPC pass-through for Solana mainnet') and enumerates the exact allowed methods, so an agent knows precisely what it can call. It also explicitly names the sibling it is not (rpc_evm) with the condition that selects it.

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?

Gives explicit when-not rules: write methods and getProgramAccounts are refused, and rpc_evm is the alternative when the need is multi-chain EVM JSON-RPC. The agent has no inference left to make about routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources