Skip to main content
Glama

A Solana account: lamports and SOL with a USD value, owner

solana_account
Read-only

A Solana account: lamports and SOL with a USD value, owner program, executable flag and data size. Token accounts and mints are parsed (mint, owner, amount and decimals; supply and authorities). Read-only over Solana JSON-RPC. Related tools on this server, for a different need: solana_wallet when you need Solana wallet holdings: SOL and every SPL / Token-2022; solana_quote when you need Best Jupiter swap route for a Solana token pair. 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": {
      "address": "<address>"
    },
    "name": "solana_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesAccount or mint address, base58

Output Schema

NameRequiredDescriptionDefault
solNo
usdNo
ownerNo
parsedNo
sourceNo
addressNo
lamportsNo
checkedAtNo
dataBytesNo
disclaimerNo
executableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description reinforces read-only access over Solana JSON-RPC while adding genuinely new behavior: token accounts and mints are auto-parsed into mint/owner/amount/decimals and supply/authorities. The cost model is disclosed in unusual detail — $0.002 per successful call via x402 USDC on multiple chains, with failed calls not charged — which an agent needs to reason about spend. It stops short of 5 by not describing failure modes such as an unparseable or non-existent address.

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?

Content is front-loaded with return fields, then sibling routing, then price — a sensible order with no filler sentences. The phrase 'Related tools on this server, for a different need' is slightly verbose scaffolding, and the parenthetical field lists make the first sentence dense, but nothing is redundant.

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?

An output schema exists, so enumerating return fields was optional, yet the description covers both the plain-account and parsed token/mint shapes. Input meaning and cost are both addressed. The remaining gap is minor: no mention of what happens for an invalid, closed, or non-existent address, which matters for a paid live-RPC call.

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?

The single parameter is fully documented in the schema as 'Account or mint address, base58', so the schema already carries the semantics. The description's note that token accounts and mints are parsed adds only a light confirmation that mint addresses are valid inputs; it provides no format, length, or encoding guidance beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The definition names a specific resource (a Solana account) and enumerates exactly what is returned: lamports, SOL + USD value, owner program, executable flag, data size, plus parsed token-account and mint fields. It explicitly distinguishes itself from solana_wallet and solana_quote. It never states an action verb like 'fetch' or 'look up', which keeps it just short of a 5.

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

Usage Guidelines4/5

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

It gives explicit routing for the two closest siblings: solana_wallet 'when you need Solana wallet holdings' and solana_quote 'when you need Best Jupiter swap route'. What is only implied is the positive case for this tool itself — look up a single account or mint by address — and there are no stated exclusions or error conditions beyond pricing.

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