Skip to main content
Glama

get-soon-mainnet-account-tokens

Retrieve token holdings for a SOON mainnet address to view account balances and token information on the SVM blockchain.

Instructions

Get the tokens of a address on the Soon mainnet

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesThe SOON address to get the tokens of

Implementation Reference

  • Handler function that retrieves token accounts owned by the given address on the Soon mainnet using Solana RPC.
    async ({ address }) => {
      try {
        const tokens = await connectionMainnet.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 defining the 'address' parameter for the tool.
    {
      address: z.string().describe("The SOON address to get the tokens of"),
    },
  • src/index.ts:207-244 (registration)
    MCP server.tool registration including name, description, input schema, and handler function.
    server.tool(
      "get-soon-mainnet-account-tokens",
      "Get the tokens of a address on the Soon mainnet",
      {
        address: z.string().describe("The SOON address to get the tokens of"),
      },
      async ({ address }) => {
        try {
          const tokens = await connectionMainnet.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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it 'Get[s] the tokens' but doesn't clarify what 'tokens' entails (e.g., token types, formats, or if it includes metadata), whether it's a read-only operation, potential rate limits, authentication needs, or error conditions. This leaves significant gaps for an agent to understand 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, clear sentence that directly states the tool's purpose without any unnecessary words. It's front-loaded and efficiently communicates the core action, making it easy to parse quickly. There's no wasted space or redundant information.

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. It doesn't explain what 'tokens' includes (e.g., token lists, balances, or metadata), how results are structured, or any behavioral traits like read-only status. For a tool with no structured context beyond the input schema, this leaves the agent with insufficient information to fully understand the tool's operation and output.

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 input schema has 100% description coverage, with the single parameter 'address' documented as 'The SOON address to get the tokens of'. The description doesn't add any meaning beyond this, such as address format examples or validation rules. With high schema coverage, the baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

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 verb ('Get') and resource ('tokens of a address on the Soon mainnet'), making the purpose immediately understandable. However, it doesn't explicitly distinguish this from its sibling tools like 'get-soon-mainnet-balance' or 'get-soon-testnet-account-tokens', which would require mentioning specific differences in what 'tokens' means versus 'balance' or 'last-transaction'.

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 when to choose this over sibling tools like 'get-soon-mainnet-balance' (which might retrieve a different type of data) or 'get-soon-testnet-account-tokens' (which targets a different network). There are no explicit usage contexts or exclusions provided.

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