Skip to main content
Glama
Sign In
Corvus

Corvus

by Allen-Saji
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_sol_balance

Retrieve SOL balance of any Solana wallet address. Displays the amount in SOL and its current USD value.

Instructions

Get the SOL balance of a Solana wallet address. Returns the balance in SOL and its current USD value. Use this when the user asks specifically about SOL balance, not other tokens.

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": {
      "wallet": "<wallet>"
    },
    "name": "get_sol_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYesBase58 Solana wallet address (32-44 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It describes the return value (balance in SOL and USD value), which is useful. However, it does not disclose any additional behavioral traits such as network dependencies, error conditions, or whether it is read-only.

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 concise with two sentences. It is front-loaded with the core function and includes usage guidance. No extraneous words.

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?

For a simple balance-checking tool with one parameter and no output schema, the description adequately explains what it returns (balance in SOL and USD value). The context signals and sibling tools provide additional orientation. No gaps.

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 description coverage is 100% (the 'wallet' parameter is described as 'Base58 Solana wallet address (32-44 characters)'). The description adds no additional parameter meaning beyond what the schema provides, which is sufficient. Baseline score of 3 applies.

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?

The description clearly states the tool gets the SOL balance of a Solana wallet and returns balance in SOL and USD value. It explicitly distinguishes from siblings by noting 'Use this when the user asks specifically about SOL balance, not other tokens.'

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?

The description provides clear context on when to use ('when the user asks specifically about SOL balance') and implies when not to use ('not other tokens'). However, it does not explicitly name alternative tools or provide detailed when-not scenarios.

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