Skip to main content
Glama

get-soon-testnet-last-transaction

Retrieve the most recent transaction for a specified address on the SOON testnet blockchain using the SVM-MCP server.

Instructions

Get the last transaction of an address on the Soon testnet

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesThe SOON address to get the last transaction for

Implementation Reference

  • Handler function that gets the latest transaction signature for the address using getSignaturesForAddress (limit 1), then fetches the confirmed transaction details, handles no transactions or errors, and returns JSON stringified transaction or error message.
    async ({ address }) => {
      try {
        const signatures = await connectionTestnet.getSignaturesForAddress(
          new PublicKey(address),
          { limit: 1 }
        );
    
        if (signatures.length === 0) {
          return {
            content: [
              {
                type: "text",
                text: "No transactions found for this address",
              },
            ],
          };
        }
    
        const latestSignature = signatures[0].signature;
        const transaction = await connectionTestnet.getConfirmedTransaction(
          latestSignature
        );
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(transaction),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Error getting transaction: ${
                error instanceof Error ? error.message : String(error)
              }`,
            },
          ],
        };
      }
    }
  • Zod input schema requiring a single 'address' string parameter with description.
    {
      address: z
        .string()
        .describe("The SOON address to get the last transaction for"),
    },
  • src/index.ts:41-93 (registration)
    Registration of the tool via server.tool(), specifying name, description, input schema, and inline handler function.
    server.tool(
      "get-soon-testnet-last-transaction",
      "Get the last transaction of an address on the Soon testnet",
      {
        address: z
          .string()
          .describe("The SOON address to get the last transaction for"),
      },
      async ({ address }) => {
        try {
          const signatures = await connectionTestnet.getSignaturesForAddress(
            new PublicKey(address),
            { limit: 1 }
          );
    
          if (signatures.length === 0) {
            return {
              content: [
                {
                  type: "text",
                  text: "No transactions found for this address",
                },
              ],
            };
          }
    
          const latestSignature = signatures[0].signature;
          const transaction = await connectionTestnet.getConfirmedTransaction(
            latestSignature
          );
    
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(transaction),
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error getting transaction: ${
                  error instanceof Error ? error.message : String(error)
                }`,
              },
            ],
          };
        }
      }
    );
  • src/index.ts:12-19 (registration)
    Tool name listed in the McpServer capabilities array.
    capabilities: [
      "get-soon-testnet-balance",
      "get-soon-testnet-last-transaction",
      "get-soon-testnet-account-tokens",
      "get-soon-mainnet-balance",
      "get-soon-mainnet-last-transaction",
      "get-soon-mainnet-account-tokens",
    ],
  • Testnet RPC connection instance used by the tool's handler for Solana queries.
    const connectionTestnet = new Connection("https://rpc.testnet.soo.network/rpc");
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. It states what the tool does but lacks behavioral details such as error handling, rate limits, authentication requirements, or what 'last transaction' means (e.g., most recent by time, by block). This leaves gaps for an AI agent to understand operational context.

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 with no wasted words. It's front-loaded with the core purpose, making it highly efficient and easy to parse.

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

Completeness3/5

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

For a simple read operation with one parameter and no output schema, the description is adequate but minimal. It covers the basic purpose but lacks context on behavior, usage, or output format, which could hinder an AI agent's ability to use it effectively without trial and error.

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%, with the single parameter 'address' well-documented in the schema. The description doesn't add any additional meaning beyond what's in the schema, such as address format or validation rules, so it meets the baseline for high schema coverage.

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 ('last transaction of an address on the Soon testnet'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from its sibling 'get-soon-mainnet-last-transaction' beyond the network name, which could be inferred but isn't stated.

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. While it's implied this is for testnet transactions, there's no explicit mention of when to choose it over mainnet tools or other testnet tools like 'get-soon-testnet-balance'.

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