Skip to main content
Glama

waiaas_get_health_factor

Check lending health factor status (safe, warning, danger, critical) for a wallet on specified blockchain networks to monitor DeFi position risk.

Instructions

Get lending health factor (safe/warning/danger/critical).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wallet_idNoTarget wallet ID. Required for multi-wallet sessions; auto-resolved when session has a single wallet.
networkNoTarget network for health factor query.

Implementation Reference

  • The 'waiaas_get_health_factor' tool handler defined within the registerGetHealthFactor function. It calls the '/v1/wallet/health-factor' API endpoint.
    server.tool(
      'waiaas_get_health_factor',
      withWalletPrefix('Get lending health factor (safe/warning/danger/critical).', walletContext?.walletName),
      {
        wallet_id: z.string().optional().describe('Target wallet ID. Required for multi-wallet sessions; auto-resolved when session has a single wallet.'),
        network: z.string().optional().describe('Target network for health factor query.'),
      },
      async (args) => {
        const params = new URLSearchParams();
        if (args.wallet_id) params.set('wallet_id', args.wallet_id);
        if (args.network) params.set('network', args.network);
        const qs = params.toString();
        const result = await apiClient.get('/v1/wallet/health-factor' + (qs ? '?' + qs : ''));
        return toToolResult(result);
      },
    );
Behavior3/5

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

No annotations provided, but description adds return category context (safe/warning/danger/critical) suggesting categorical enum output. Lacks details on calculation methodology, thresholds, or error states.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely compact at 7 words with purpose front-loaded. No redundancy, though brevity limits behavioral disclosure.

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?

Adequate for a simple read operation with 2 parameters, but missing: valid network values, explanation of health factor semantics, and whether absence of lending position returns an error or null.

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 coverage is 100% (both wallet_id and network have descriptions), establishing baseline 3. Description adds no parameter-specific context, relying entirely on schema documentation.

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?

Clear verb 'Get' and specific resource 'lending health factor' distinguishes this from sibling get_balance/get_assets tools. The parenthetical hints at return values but doesn't fully differentiate from waiaas_get_defi_positions.

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 on when to use versus waiaas_get_defi_positions or other portfolio tools. No mention of prerequisites like requiring an active lending position.

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