Skip to main content
Glama

get-soon-mainnet-balance

Check the SOON mainnet balance for any address to monitor cryptocurrency holdings on the SVM blockchain.

Instructions

Get the balance of a address on the Soon mainnet

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesThe SOON address to get the balance of

Implementation Reference

  • The handler function that retrieves the Soon mainnet balance for the given address using Solana's connectionMainnet.getBalance and returns it as formatted text.
    async ({ address }) => {
      const balance = await connectionMainnet.getBalance(new PublicKey(address));
      return {
        content: [
          {
            type: "text",
            text: `Balance: ${balance}`,
          },
        ],
      };
    }
  • Zod schema for input validation: requires a string 'address' parameter.
    {
      address: z.string().describe("The SOON address to get the balance of"),
    },
  • src/index.ts:134-151 (registration)
    Full tool registration call including name, description, schema, and handler function.
    server.tool(
      "get-soon-mainnet-balance",
      "Get the balance of a address on the Soon mainnet",
      {
        address: z.string().describe("The SOON address to get the balance of"),
      },
      async ({ address }) => {
        const balance = await connectionMainnet.getBalance(new PublicKey(address));
        return {
          content: [
            {
              type: "text",
              text: `Balance: ${balance}`,
            },
          ],
        };
      }
    );
  • RPC connection to Soon mainnet used in the balance handler.
    const connectionMainnet = new Connection("https://rpc.mainnet.soo.network/rpc");
  • src/index.ts:16-16 (registration)
    Tool name listed in server capabilities.
    "get-soon-mainnet-balance",
Behavior2/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 of behavioral disclosure. While it indicates a read operation ('Get'), it lacks details on potential errors (e.g., invalid addresses), rate limits, network dependencies, or response format. This leaves significant gaps in understanding how the tool behaves beyond its basic function.

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, direct sentence that efficiently conveys the core purpose without unnecessary words. It is front-loaded with the essential action and resource, making it highly concise and well-structured for quick comprehension.

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 a tool that interacts with a blockchain network. It doesn't cover error handling, return value details (e.g., balance units or format), or network-specific considerations, which are crucial for effective agent use in this 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 schema description coverage is 100%, with the single parameter 'address' clearly documented in the schema. The description adds no additional semantic context beyond what the schema provides, such as address format examples or validation rules, so it meets the baseline for adequate but not enhanced parameter understanding.

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 mainnet'), making the purpose immediately understandable. However, it doesn't explicitly distinguish this tool from its sibling 'get-soon-testnet-balance', which performs the same function on a different network, leaving some ambiguity about when to choose one over the other.

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 the sibling tools, such as 'get-soon-testnet-balance' for testnet addresses or 'get-soon-mainnet-account-tokens' for token-specific queries, leaving the agent to infer usage context without explicit direction.

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