Skip to main content
Glama

get_recent_transactions

Retrieve recent transaction history for an agent wallet to monitor blockchain activity and track financial operations.

Instructions

Get recent transactions for the agent wallet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of transactions to return (default: 10)

Implementation Reference

  • MCP tool handler for 'get_recent_transactions': parses arguments, calls wallet method, formats response as JSON.
    case "get_recent_transactions": {
      const { limit = 10 } = args as { limit?: number };
      const transactions = await wallet.getRecentTransactions(limit);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(transactions, null, 2),
          },
        ],
      };
    }
  • src/index.ts:65-78 (registration)
    Tool registration including name, description, and input schema definition.
    {
      name: "get_recent_transactions",
      description: "Get recent transactions for the agent wallet.",
      inputSchema: {
        type: "object",
        properties: {
          limit: {
            type: "number",
            description: "Maximum number of transactions to return (default: 10)",
          },
        },
        required: [],
      },
    },
  • Implements the core logic: fetches recent transaction signatures via Solana RPC and maps to simplified TransactionInfo objects.
    async getRecentTransactions(limit: number = 10): Promise<TransactionInfo[]> {
      const signatures = await this.connection.getSignaturesForAddress(
        this.keypair.publicKey,
        { limit }
      );
    
      return signatures.map((sig) => ({
        signature: sig.signature,
        timestamp: sig.blockTime,
        status: sig.err ? "failed" : "success",
        type: "transaction",
      }));
    }
  • Type definition for transaction information returned by the tool.
    export interface TransactionInfo {
      signature: string;
      timestamp: number | null | undefined;
      status: "success" | "failed";
      type: string;
    }
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 action but doesn't explain key traits like whether this is a read-only operation, if it requires authentication, rate limits, or what the return format looks like (e.g., list of transactions with details). This leaves significant gaps in understanding how the tool behaves.

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 directly states the tool's purpose without any wasted words. It is appropriately sized and front-loaded, 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 lack of annotations and output schema, the description is incomplete for a tool that retrieves data. It doesn't specify what 'recent' means (e.g., time frame), the structure of returned transactions, or any error conditions, leaving the agent with insufficient context to use the tool effectively.

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 'limit' parameter well-documented in the schema itself. The description adds no additional meaning beyond implying retrieval of 'recent' transactions, which is already suggested by the tool name. This meets the baseline for high schema coverage without extra value.

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 ('recent transactions for the agent wallet'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_balance' or 'send_usdc', which also involve wallet operations, so it doesn't reach the highest clarity level.

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 like 'get_balance' or 'send_usdc'. It lacks context about scenarios where retrieving transactions is appropriate, such as for auditing or tracking payments, leaving the agent to infer usage.

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/noah-ing/agent-wallet-mcp'

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