Skip to main content
Glama
clumsynonono

Aave Liquidation MCP Server

by clumsynonono

validate_address

Verify Ethereum address format for Aave V3 protocol interactions to ensure accurate transaction processing and data queries.

Instructions

Validate if a string is a valid Ethereum address format.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesAddress string to validate

Implementation Reference

  • src/index.ts:147-161 (registration)
    Tool registration in the listTools response, including name, description, and input schema definition.
    {
      name: 'validate_address',
      description:
        'Validate if a string is a valid Ethereum address format.',
      inputSchema: {
        type: 'object',
        properties: {
          address: {
            type: 'string',
            description: 'Address string to validate',
          },
        },
        required: ['address'],
      },
    },
  • The main tool handler in the CallToolRequestSchema switch statement. Validates input, calls the helper method, and formats the response.
    case 'validate_address': {
      const address = args?.address as string;
      if (!address || typeof address !== 'string') {
        throw new McpError(
          ErrorCode.InvalidParams,
          'address parameter is required and must be a string'
        );
      }
    
      const isValid = aaveClient.isValidAddress(address);
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(
              {
                address,
                isValid,
                message: isValid
                  ? 'Valid Ethereum address format'
                  : 'Invalid Ethereum address format',
              },
              null,
              2
            ),
          },
        ],
      };
    }
  • Core helper method that performs the actual Ethereum address validation using ethers.js utility.
    isValidAddress(address: string): boolean {
      return ethers.isAddress(address);
    }
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 tool validates format but does not specify what constitutes a valid Ethereum address (e.g., checksum, length), whether it performs network checks, or what the output looks like (e.g., boolean, error details). This leaves significant gaps for a tool with no annotation coverage.

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 front-loads the core purpose without unnecessary words. It directly states the tool's function, making it easy to parse and understand 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. It does not explain the validation criteria, return values, or error handling, which are critical for understanding how to use this tool effectively. The description alone is insufficient for a tool with no structured behavioral data.

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%, so the input schema already documents the single parameter 'address' as a string to validate. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or validation rules, meeting the baseline for high schema coverage.

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?

The description clearly states the specific action ('validate') and resource ('Ethereum address format'), distinguishing it from siblings like batch_check_addresses (which handles multiple addresses) or get_user_positions (which retrieves user data). It precisely communicates the tool's function without ambiguity.

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?

The description implies usage for validating Ethereum addresses, but provides no explicit guidance on when to use this tool versus alternatives like batch_check_addresses for multiple addresses or other siblings for unrelated tasks. It lacks context on prerequisites or exclusions.

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/clumsynonono/aave-liquidation-mcp'

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