Skip to main content
Glama
minhoyoo-iotrust

waiaas

by minhoyoo-iotrust
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

get_assets

Retrieve all assets including native tokens and tokens held by a wallet across multiple blockchain networks, with value conversion to specified currencies.

Instructions

Get all assets (native + tokens) held by the wallet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkNoQuery assets for specific network (e.g., "polygon-mainnet" or CAIP-2 "eip155:137"). Use "all" for all networks. Required for EVM wallets; auto-resolved for Solana.
display_currencyNoDisplay currency for asset value conversion (e.g. KRW, EUR). Defaults to server setting.
wallet_idNoTarget wallet ID. Required for multi-wallet sessions; auto-resolved when session has a single wallet.

Implementation Reference

  • packages/mcp/src/tools/get-assets.ts:10-29 (handler)
    The `registerGetAssets` function registers the 'get_assets' MCP tool. Its internal handler function calls the `/v1/wallet/assets` API endpoint to retrieve wallet assets.
    export function registerGetAssets(server: McpServer, apiClient: ApiClient, walletContext?: WalletContext): void {
  server.tool(
    'get_assets',
    withWalletPrefix('Get all assets (native + tokens) held by the wallet.', walletContext?.walletName),
    {
      network: z.string().optional().describe('Query assets for specific network (e.g., "polygon-mainnet" or CAIP-2 "eip155:137"). Use "all" for all networks. Required for EVM wallets; auto-resolved for Solana.'),
      display_currency: z.string().optional().describe('Display currency for asset value conversion (e.g. KRW, EUR). Defaults to server setting.'),
      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.network) params.set('network', args.network);
      if (args.display_currency) params.set('display_currency', args.display_currency);
      if (args.wallet_id) params.set('walletId', args.wallet_id);
      const qs = params.toString();
      const result = await apiClient.get('/v1/wallet/assets' + (qs ? '?' + qs : ''));
      return toToolResult(result);
    },
  );
}

Tool Definition Quality

B3.1/5.0
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, yet it only mentions that the tool returns 'native + tokens'. It omits critical behavioral traits: whether results are paginated, cached, or real-time; rate limiting; required permissions; or response format structure. The 'Get' verb implies read-only, but this is not explicitly confirmed.

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?

At nine words, the description is maximally efficient. Every element earns its place: action verb ('Get'), scope quantifier ('all'), resource ('assets'), parenthetical clarification ('native + tokens'), and target ('held by the wallet'). Information is front-loaded with no redundancy.

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?

Given three parameters, 100% schema coverage, and no output schema, the description meets minimum viability by clarifying the asset types returned (native + tokens). However, it lacks return value documentation that could compensate for the missing output schema, and fails to address the complex sibling landscape of wallet query tools.

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?

With 100% schema description coverage, the schema fully documents all three parameters (network, display_currency, wallet_id), including conditional requirements and examples. The description adds no parameter-specific guidance, but the high schema coverage establishes a baseline score of 3.

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 'Get all assets (native + tokens) held by the wallet' clearly states the verb (Get), resource (assets), and scope (all, specifically native + tokens). The parenthetical clarification helpfully distinguishes from NFT-only queries (list_nfts) and implies broader coverage than single-asset queries (get_balance). However, it does not explicitly differentiate from the sibling tool 'get_tokens', leaving potential ambiguity.

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 siblings like 'get_tokens', 'get_balance', or 'waiaas_pm_get_balance'. There is no mention of prerequisites, session requirements, or specific use cases where this is preferred over narrower asset queries.

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