Skip to main content
Glama

get-soon-testnet-balance

Check the SOON testnet balance for any address to monitor account funds and verify transactions on the SVM blockchain.

Instructions

Get the balance of a address on the Soon testnet

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesThe SOON address to get the balance of

Implementation Reference

  • Handler function that retrieves the SOON testnet balance for the given address using Solana's connectionTestnet.getBalance.
    async ({ address }) => {
      const balance = await connectionTestnet.getBalance(new PublicKey(address));
      return {
        content: [
          {
            type: "text",
            text: `Balance: ${balance}`,
          },
        ],
      };
  • Input schema defining the 'address' parameter as a string.
    {
      address: z.string().describe("The SOON address to get the balance of"),
    },
  • src/index.ts:22-39 (registration)
    Registers the 'get-soon-testnet-balance' tool with McpServer, including schema and inline handler.
    server.tool(
      "get-soon-testnet-balance",
      "Get the balance of a address on the Soon testnet",
      {
        address: z.string().describe("The SOON address to get the balance of"),
      },
      async ({ address }) => {
        const balance = await connectionTestnet.getBalance(new PublicKey(address));
        return {
          content: [
            {
              type: "text",
              text: `Balance: ${balance}`,
            },
          ],
        };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic function. It doesn't disclose behavioral traits such as whether this is a read-only operation (implied but not explicit), rate limits, error conditions, or what format the balance is returned in (e.g., native units, decimals). This leaves significant gaps for safe and effective use.

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 a single, efficient sentence that front-loads the core purpose without any wasted words. It's appropriately sized for a simple tool with one parameter, making it easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete for effective use. It doesn't explain what the balance output looks like (e.g., numeric value, currency), potential errors, or network-specific behaviors, which are crucial for a financial query tool in a blockchain context.

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 description adds no parameter semantics beyond what the input schema provides, which has 100% coverage with a clear description for the single 'address' parameter. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 description clearly states the action ('Get the balance') and resource ('address on the Soon testnet'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from its sibling 'get-soon-mainnet-balance' beyond the network name, which is implied but not stated as a distinguishing factor.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'get-soon-mainnet-balance' for mainnet queries or 'get-soon-testnet-account-tokens' for token-specific balances, leaving the agent to infer usage context solely from the tool name.

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/rkmonarch/svm-mcp'

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