Skip to main content
Glama

get-soon-testnet-account-tokens

Retrieve token holdings for a specific address on the SOON testnet to view balances and assets in the SVM blockchain ecosystem.

Instructions

Get the tokens of a address on the Soon testnet

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesThe SOON address to get the tokens of

Implementation Reference

  • Handler function fetches token accounts by owner on Soon testnet using Solana Web3.js and returns JSON or error message.
    async ({ address }) => {
      try {
        const tokens = await connectionTestnet.getTokenAccountsByOwner(
          new PublicKey(address),
          {
            programId: new PublicKey(
              "TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA"
            ),
          }
        );
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(tokens),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Error getting tokens: ${
                error instanceof Error ? error.message : String(error)
              }`,
            },
          ],
        };
      }
    }
  • Zod input schema requiring a 'address' string parameter.
    {
      address: z.string().describe("The SOON address to get the tokens of"),
    },
  • src/index.ts:95-132 (registration)
    Full tool registration with server.tool(), including name, description, schema, and handler.
    server.tool(
      "get-soon-testnet-account-tokens",
      "Get the tokens of a address on the Soon testnet",
      {
        address: z.string().describe("The SOON address to get the tokens of"),
      },
      async ({ address }) => {
        try {
          const tokens = await connectionTestnet.getTokenAccountsByOwner(
            new PublicKey(address),
            {
              programId: new PublicKey(
                "TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA"
              ),
            }
          );
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(tokens),
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error getting tokens: ${
                  error instanceof Error ? error.message : String(error)
                }`,
              },
            ],
          };
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves tokens but doesn't specify what 'tokens' entails (e.g., token types, amounts, or metadata), whether it's a read-only operation, potential rate limits, or error conditions. This leaves significant gaps in understanding the tool's behavior beyond the basic action.

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 action without unnecessary words. It is front-loaded and appropriately sized for the tool's complexity, making it easy 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 tool's moderate complexity (a read operation with one parameter) and the absence of annotations and output schema, the description is incomplete. It doesn't clarify what 'tokens' means in the return value, how results are formatted, or any behavioral nuances, leaving the agent with insufficient context for effective use.

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 or validation rules. Since the schema handles the parameter documentation adequately, a baseline score of 3 is appropriate.

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') and resource ('tokens of an address on the Soon testnet'), making the purpose understandable. However, it doesn't explicitly differentiate from its sibling tools like 'get-soon-testnet-balance' or 'get-soon-mainnet-account-tokens', which would require specifying what 'tokens' means in this context versus 'balance' or other network variants.

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?

No guidance is provided on when to use this tool versus alternatives. Given the sibling tools include similar functions for testnet and mainnet (e.g., 'get-soon-testnet-balance', 'get-soon-mainnet-account-tokens'), the description lacks explicit instructions on selection criteria, such as network differences or token vs. balance distinctions.

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