NELQIRO · Tools

Tools

Explore Solana account data, transaction analysis and protocol mechanics. The names below are reference schemas for integration design. Each group links to documentation, and the examples explain inputs and results for a separately configured service.

01

The catalogue

Reference schemas, design patterns and protocol mechanics

Group 01Reference
Group 01

Read and simulate

Nine reference schemas describe Solana account, token, transaction and network data, plus transaction simulation. They explain RPC inputs and outputs for a separately configured service.

Scope

Public identifiers are enough for reads. Simulation takes serialized transaction bytes.

solana_get_balance

Read an address's SOL balance. Keep the raw lamport amount alongside the SOL value.

solana_get_token_balances

List token accounts, mint addresses, decimals and balances for SPL Token and Token-2022.

solana_get_account_info

Inspect an account's owner program, lamports, executable flag and available parsed data.

solana_get_signatures

Page through signatures involving an address, with confirmation state and errors.

solana_get_transaction

Inspect a confirmed transaction's message, instructions, balances, fees and available logs.

solana_get_signature_status

Check a signature's confirmation status and execution error at a chosen commitment.

solana_get_token_supply

Read a mint's supply in base units, its decimals and the corresponding display amount.

solana_network_status

Understand RPC health, slot, epoch and version. Each result belongs to a particular RPC node.

solana_simulate_transaction

Review simulation errors, logs and compute usage for serialized transaction bytes.

Read the reference →
Group 02Reference
Group 02

Understand

Read the structure of a transaction and compare its intended effects with the available chain data. Simulation, decoding and log inspection answer different questions and carry different limits.

Scope

Read-only analysis uses public data or supplied transaction bytes.

solana_simulate_transaction

Review a simulation at the requested commitment. State may change before execution, and missing signatures affect what can be checked.

ExampleInspect the logs and compute use for these transaction bytes.
solana_decode_transaction

Identify the fee payer, signers, program IDs, account roles and instruction data. Program-specific decoding needs a known instruction format.

ExampleExplain the accounts and instructions in this transaction.
solana_trace_call

Relate available inner instructions and program logs to the reported error. RPC history may omit details, so report gaps in the evidence.

ExampleWhich program logged the failure in this transaction?
Read the reference →
Group 03Design
Group 03

Build

A development workflow starts with reviewed Rust or Anchor source, reports compiler diagnostics, estimates transaction costs and verifies deployed binaries. These schemas outline a developer integration.

Scope

Compilation is local. Deployment authority and upgrade authority require explicit control.

solana_scaffold

Describe a Rust or Anchor project layout, dependencies and program authority model. Templates need review for the intended use.

ExampleOutline a simple Anchor program and its account constraints.
solana_program_build

Specify compiler input, pinned toolchain and diagnostics for a repeatable Solana program build.

ExampleExplain the compiler errors in this Anchor project.
solana_estimate_fees

Separate signature fees, priority fees and account funding. Estimates depend on the message and current network state.

ExampleWhich fees and account deposits would this transaction require?
solana_deploy

Document program deployment, buffer accounts, fee payer and upgrade authority before the developer signs.

ExampleReview the authorities needed to deploy this program.
solana_verify

Compare a reproducible source build with a deployed program binary and identify the verified release.

ExampleHow can I check that this source matches the deployed binary?
Read the reference →
Group 04Design
Group 04

Act

Transaction preparation, signing, submission and confirmation are separate steps. This design reference makes the required authorities, network and expected account changes explicit at each step.

Scope

A user's wallet or an explicitly authorized program controls every state-changing action.

solana_prepare_transaction

Describe an unsigned message with its fee payer, recipient, programs, amounts and recent blockhash for review.

ExampleReview the accounts and amount in this proposed SOL transfer.
solana_prepare_batch

Explain instruction ordering, shared accounts and atomicity limits. Separate transactions can succeed or fail independently.

ExampleCan these instructions fit in one atomic Solana transaction?
solana_send_signed

Document submission of already signed bytes and distinguish RPC acceptance from chain confirmation.

ExampleWhat checks are needed before submitting signed bytes?
solana_wait

Describe confirmation by signature, commitment and blockhash validity, including expiry and execution errors.

ExampleHow should an application handle an expired transaction?
solana_key_status

Inspect the authority model of a chosen wallet program. Spending caps and expiry exist only if that program enforces them.

ExampleWhich permissions does this delegated authority actually have?
solana_agent_wallet

Model delegated permissions, revocation, fee funding and monitoring for a selected smart-wallet implementation.

ExampleDesign a daily spending limit and a revocation path.
Read the reference →
Group 05Design
Group 05

Agents

Agent integrations need explicit identity, service discovery, payment authorization and event processing. The examples describe application designs and avoid assuming a single Solana agent registry or reputation standard.

Scope

Public lookups are read-only. Registration and payments depend on the selected application.

solana_agent_register

Define a registration record, owner authority and service endpoints for a chosen registry implementation.

ExampleWhat fields should an agent's service registration contain?
solana_agent_lookup

Describe discovery by owner, service or identifier, with the registry and data provenance included.

ExampleHow can I verify the owner of this agent record?
solana_agent_feedback

Design feedback attribution, conflicts of interest and abuse controls for a reputation system.

ExampleHow should a client distinguish verified feedback from self-reviews?
solana_agent_pay

Specify asset mint, recipient, amount and authorization for a payment. Recurring payments need a separate execution mechanism.

ExampleReview a USDC payment's mint, recipient and amount.
solana_agent_job

Model escrow conditions, deadlines, dispute authority and refunds in a reviewed application program.

ExampleWhich parties control release and refund in this escrow?
solana_watch

Describe account subscriptions or indexed events, reconnection, deduplication and commitment handling.

ExampleHow should a watcher handle dropped WebSocket connections?
solana_react

Separate event detection from policy checks, transaction preparation and explicit signing authority.

ExampleDesign a review step before an event triggers a payment.
solana_index

Define a historical data source, pagination and reconciliation against finalized chain records.

ExampleWhich indexed records support this transaction summary?
Read the reference →
Group 06Mechanics
Group 06

Drift perps

Drift perpetuals use Solana accounts, oracle prices, margin and funding. Liquidity can come from its decentralized orderbook, just-in-time makers and AMM. The reference separates market data from order execution.

Scope

Market data is public. Orders and delegated authority follow Drift's program rules.

solana_perps_markets

Describe Drift market indices, oracle prices, funding, open interest and market-specific margin parameters.

ExampleWhich fields identify a Drift perpetual market?
solana_perps_market

Inspect available DLOB orders, AMM state and oracle context. Depth and execution estimates depend on the data source and time.

ExampleHow do oracle price and available liquidity affect an order?
solana_perps_account

Read collateral, spot balances, perp positions, open orders and margin health for a Drift subaccount.

ExampleWhat contributes to this subaccount's maintenance margin?
solana_perps_funding

Explain Drift funding payments and history, recording the market and observation time for each value.

ExampleHow does funding change the cost of holding this position?
solana_perps_candles

Describe OHLCV intervals and source timestamps. Missing trades or history affect derived indicators.

ExampleWhat data is needed for a four-hour SOL candle?
solana_perps_risk

Explain collateral weights, maintenance requirements, oracle changes and liquidation scenarios.

ExampleHow would a price move affect this account's margin?
solana_perps_plan

Specify market, direction, size, limit and trigger conditions before an order is reviewed and signed.

ExampleReview the size and trigger conditions in a proposed order.
solana_perps_scan

Compare observed funding, open interest and price changes with explicit timestamps and selection rules.

ExampleWhich market measurements should a funding comparison include?
solana_perps_backtest

Outline a reproducible historical model including fees, funding, slippage and unavailable data.

ExampleWhich assumptions affect a moving-average backtest?
solana_perps_agent

Explain Drift delegation and the actions permitted by the chosen authority. Application limits require separate enforcement.

ExampleWhich actions can this Drift delegate perform?
solana_perps_submit

Document signed order submission, expiry, confirmation and error handling for an external Drift integration.

ExampleHow should an application track an order after submission?
Read the reference →
Group 07Design
Group 07

Privacy and data

Solana account activity is publicly observable. Privacy designs must specify the additional protocol, threat model and metadata exposure. Local preparation alone does not conceal an on-chain sender, recipient or amount.

Scope

Signatures authorize actions. Local secrets, off-chain records and public chain data have distinct risks.

solana_private_pool

Outline the assets, contract audits, anonymity assumptions and deposit data required to assess a separate privacy protocol.

ExampleWhich assumptions would a privacy pool depend on?
solana_private_deposit

Describe an external protocol's deposit and secret-handling requirements. An ordinary Solana transfer remains public.

ExampleWhat metadata would this deposit expose on chain?
solana_private_withdraw

Review proof verification, recipient choice, timing and relayer trust for an explicitly selected privacy protocol.

ExampleWhich withdrawal details could link two public addresses?
solana_private_invoice

Design off-chain invoice contents and disclosure rules while distinguishing them from the settlement transaction.

ExampleWhich invoice fields should remain off chain?
solana_private_risk

Explain timing, amount, address-reuse and network metadata correlations without assigning an unsupported privacy score.

ExampleCould address reuse link these transactions?
solana_private_disclose

Describe scoped disclosure and proof verification for a protocol that supports selective audit records.

ExampleWhat evidence should a scoped disclosure contain?
solana_private_session

Review separate-address key management, funding links and cleanup. A fresh address can still be correlated.

ExampleHow can funding activity reveal a new address's owner?
Read the reference →
Group 08Mechanics
Group 08

Jupiter Swap

Jupiter aggregates token-swap liquidity on Solana. Quotes describe routes, amounts, fees and execution constraints, while transaction instructions support a separate wallet-signing flow. Liquidity positions belong to the underlying DEX.

Scope

Quotes are read-only. A swap transaction requires the appropriate wallet authorization.

solana_jupiter_tokens

Inspect token mints, decimals and supported metadata. A symbol alone is insufficient to identify an asset.

ExampleWhich mint identifies the token in this quote?
solana_jupiter_quote

Explain input and output mints, amount in base units, route, fees and price impact in a swap quote.

ExampleWhich fees and minimum output apply to this SOL-to-USDC quote?
solana_jupiter_swap

Review an assembled swap transaction, its fee payer, source accounts and output constraints before signing.

ExampleWhich accounts will this swap debit and credit?
solana_jupiter_swap_instructions

Describe raw swap instructions for a custom transaction, including account limits and compute requirements.

ExampleWhat must be checked when combining a swap with another instruction?
solana_jupiter_route

Explain the selected liquidity venues and route splits. A route is specific to the quoted amount and current liquidity.

ExampleWhich Solana liquidity venues appear in this route?
solana_jupiter_price

Interpret price data with its mint, quote asset and timestamp. A displayed price can differ from an executable quote.

ExampleHow does this reference price compare with the swap quote?
solana_jupiter_order_status

Distinguish provider order state from Solana signature confirmation and report submission errors separately.

ExampleWhat does an accepted order say about chain confirmation?
solana_jupiter_transaction_review

Inspect programs, signers, output limits and simulation logs from a proposed Jupiter swap.

ExampleWhat should I review before signing this swap?
Read the reference →
Group 09Mechanics
Group 09

Raydium LaunchLab

LaunchLab is Raydium's token-launch product. Tokens trade along configured bonding curves before eligible launches graduate into Raydium liquidity pools. Launch parameters, fees and migration rules belong to that protocol.

Scope

Public launch information is read-only. Buying, selling and creating a launch require wallet signatures.

solana_raydium_pools

Inspect a Raydium pool or LaunchLab launch, including its program, token mints, curve state and graduation status.

ExampleHas this LaunchLab token graduated to a Raydium pool?
solana_raydium_quote

Explain a buy or sell estimate using the relevant bonding curve or pool, including fees and minimum output.

ExampleHow do curve price and fees affect this launch quote?
solana_raydium_swap

Review the appropriate LaunchLab or pool instructions, token accounts and slippage constraints for a trade.

ExampleWhich program handles this token before and after graduation?
solana_raydium_launchlab

Describe token metadata, supply allocation, curve configuration, fees and graduation settings for a launch.

ExampleWhich launch parameters and migration rules should a creator review?
Read the reference →
Group 10Mechanics
Group 10

Wormhole

Wormhole supports cross-chain messaging and token-transfer integrations, including Solana. A transfer spans source and destination chains with separate finality, verification and redemption steps. Routing support depends on the chosen product.

Scope

A source-chain transfer needs authorization. Destination completion depends on the route and relayer model.

solana_wormhole_route

Describe supported source and destination assets, fees, route providers and expected finality for a cross-chain transfer.

ExampleWhich steps and fees connect this source asset to Solana?
solana_wormhole_transfer

Track source confirmation, message attestation and destination redemption as separate stages with recoverable errors.

ExampleWhich transfer stage is waiting for destination redemption?
Read the reference →
Group 11Mechanics
Group 11

Kamino

Kamino provides Solana lending markets and vault strategies. Review reserve utilization, collateral risk, borrow positions and strategy parameters. Yields vary with market activity, fees and the selected product.

Scope

Market and position data is public. Deposits, withdrawals and borrowing require wallet authorization.

solana_kamino_markets

Inspect lending reserves, assets, utilization, variable rates and market-specific risk parameters.

ExampleHow do utilization and collateral weights affect this market?
solana_kamino_obligation

Read supplied collateral, debt and loan-to-value measures for a Kamino lending position.

ExampleWhich asset moves would raise this obligation's liquidation risk?
solana_kamino_vaults

Describe a vault's underlying strategy, assets, fees, allocations and share accounting.

ExampleWhat strategy and assets back this vault's shares?
solana_kamino_deposit

Review an unsigned deposit's token mint, amount, destination vault or reserve and expected shares.

ExampleWhich account receives the shares from this deposit?
solana_kamino_withdraw

Explain withdrawal liquidity, share redemption and collateral constraints before a transaction is signed.

ExampleCould withdrawing this collateral affect the loan's health?
Read the reference →
Group 12Mechanics
Group 12

Pyth price data

Oracle prices need a feed identifier, publish time, exponent and confidence interval. Pyth provides price-update products for Solana, each with its own verification, freshness and access requirements.

Scope

Price inspection is read-only. On-chain consumption follows the selected oracle product's verification flow.

solana_pyth_price

Describe a Pyth feed's value, confidence interval, exponent and publication time, with an explicit freshness check.

ExampleIs this SOL/USD price update recent enough for the intended use?
Read the reference →
02

Review before integration

Four checks for a clear transaction workflow

01

Simulation has limits

Inspect errors, logs and compute use. State, blockhash validity and prices can change before execution.

02

Control your keys

Keep signing keys in wallet software. Public data inspection needs only public identifiers.

03

Inspect the message

Review fee payer, signers, program IDs, amounts and instructions before authorizing a transaction.

04

Check the network

Confirm the cluster, commitment and protocol program. Each integration defines its own permissions.

Use the connection guide to understand MCP configuration and the tool reference to review the schemas. This website provides the catalogue and documentation. A deployed service must supply its own endpoint and advertised tools.