Skip to main content
Glama

get_incoming_summary

Generate period-based summaries of incoming transactions with daily, weekly, or monthly totals converted to USD for crypto wallet analysis.

Instructions

Get a period-based summary of incoming transactions (daily/weekly/monthly totals with USD conversion).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
periodNoAggregation period: daily, weekly, or monthly (default: daily)
chainNoFilter by chain (solana or ethereum)
networkNoFilter by network
sinceNoSummary start epoch (seconds)
untilNoSummary end epoch (seconds)
wallet_idNoTarget wallet ID. Required for multi-wallet sessions; auto-resolved when session has a single wallet.

Implementation Reference

  • The handler function for the 'get_incoming_summary' tool, which constructs query parameters and fetches the summary from the API.
    async (args) => {
      const params = new URLSearchParams();
      if (args.period !== undefined) params.set('period', args.period);
      if (args.chain !== undefined) params.set('chain', args.chain);
      if (args.network !== undefined) params.set('network', args.network);
      if (args.since !== undefined) params.set('since', String(args.since));
      if (args.until !== undefined) params.set('until', String(args.until));
      if (args.wallet_id) params.set('wallet_id', args.wallet_id);
      const qs = params.toString();
      const result = await apiClient.get(`/v1/wallet/incoming/summary${qs ? `?${qs}` : ''}`);
      return toToolResult(result);
    },
  • Zod schema defining the input arguments for 'get_incoming_summary'.
    {
      period: z.string().optional().describe('Aggregation period: daily, weekly, or monthly (default: daily)'),
      chain: z.string().optional().describe('Filter by chain (solana or ethereum)'),
      network: z.string().optional().describe('Filter by network'),
      since: z.number().optional().describe('Summary start epoch (seconds)'),
      until: z.number().optional().describe('Summary end epoch (seconds)'),
      wallet_id: z.string().optional().describe('Target wallet ID. Required for multi-wallet sessions; auto-resolved when session has a single wallet.'),
    },
  • Function that registers the 'get_incoming_summary' tool with the MCP server.
    export function registerGetIncomingSummary(
      server: McpServer,
      apiClient: ApiClient,
      walletContext?: WalletContext,
    ): void {
      server.tool(
        'get_incoming_summary',
        withWalletPrefix(
          'Get a period-based summary of incoming transactions (daily/weekly/monthly totals with USD conversion).',
          walletContext?.walletName,
        ),
        {
          period: z.string().optional().describe('Aggregation period: daily, weekly, or monthly (default: daily)'),
          chain: z.string().optional().describe('Filter by chain (solana or ethereum)'),
          network: z.string().optional().describe('Filter by network'),
          since: z.number().optional().describe('Summary start epoch (seconds)'),
          until: z.number().optional().describe('Summary end epoch (seconds)'),
          wallet_id: z.string().optional().describe('Target wallet ID. Required for multi-wallet sessions; auto-resolved when session has a single wallet.'),
        },
        async (args) => {
          const params = new URLSearchParams();
          if (args.period !== undefined) params.set('period', args.period);
          if (args.chain !== undefined) params.set('chain', args.chain);
          if (args.network !== undefined) params.set('network', args.network);
          if (args.since !== undefined) params.set('since', String(args.since));
          if (args.until !== undefined) params.set('until', String(args.until));
          if (args.wallet_id) params.set('wallet_id', args.wallet_id);
          const qs = params.toString();
          const result = await apiClient.get(`/v1/wallet/incoming/summary${qs ? `?${qs}` : ''}`);
          return toToolResult(result);
        },
      );
    }
Behavior3/5

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

Discloses USD conversion behavior and aggregation granularity (daily/weekly/monthly). However, with no annotations provided, omits safety profile (read-only), rate limits, and error conditions that description should disclose.

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?

Single efficient sentence, front-loaded with action and resource. Parenthetical aptly clarifies aggregation periods and output format without verbosity.

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

Completeness4/5

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

Despite no output schema, description adequately explains return value (totals with USD conversion). Misses opportunity to clarify wallet_id requirement for multi-wallet sessions, though schema covers this.

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 has 100% coverage, establishing baseline 3. Description paraphrases period options but adds minimal semantic depth beyond schema descriptions; could clarify relationships between chain/network filters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Excellent: specific verb 'Get' + resource 'summary of incoming transactions', clearly distinguishes from sibling 'list_incoming_transactions' by emphasizing aggregation ('period-based', 'totals') rather than enumeration.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implied usage through 'period-based' and 'totals' suggests aggregation use case, but lacks explicit guidance on when to choose this over 'list_incoming_transactions' or other transaction tools.

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/minhoyoo-iotrust/WAIaaS'

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