Skip to main content
Glama
clumsynonono

Aave Liquidation MCP Server

by clumsynonono

get_protocol_status

Check Aave V3 protocol status and current block number to monitor network activity and assess liquidation conditions.

Instructions

Get general Aave V3 protocol status including current block number.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main execution handler for the 'get_protocol_status' tool. It calls aaveClient.getBlockNumber() and formats a JSON response with protocol details including the current block number.
    case 'get_protocol_status': {
      const blockNumber = await aaveClient.getBlockNumber();
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(
              {
                protocol: 'Aave V3',
                network: 'Ethereum Mainnet',
                blockNumber,
                poolAddress: '0x87870Bca3F3fD6335C3F4ce8392D69350B4fA4E2',
                status: 'operational',
              },
              null,
              2
            ),
          },
        ],
      };
    }
  • Input/output schema definition for the tool, specifying no required parameters.
      name: 'get_protocol_status',
      description:
        'Get general Aave V3 protocol status including current block number.',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Supporting method in AaveClient class that retrieves the current Ethereum block number via the ethers provider.
    async getBlockNumber(): Promise<number> {
      return await this.provider.getBlockNumber();
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states it's a read operation ('Get'), implying safety, but doesn't disclose behavioral traits such as rate limits, authentication needs, error conditions, or what 'general protocol status' entails beyond block number.

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 with no wasted words. It front-loads the core purpose and includes specific details, making it easy to parse quickly.

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 the tool has no parameters, no output schema, and no annotations, the description is adequate but minimal. It covers the basic purpose but lacks details on return format, error handling, or broader context needed for full agent understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema coverage, so no parameter documentation is needed. The description adds value by specifying what information is retrieved ('general Aave V3 protocol status including current block number'), which is appropriate for a parameterless tool.

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 the resource 'general Aave V3 protocol status', including specific content 'current block number'. It doesn't explicitly differentiate from siblings like 'get_aave_reserves' or 'get_user_health', but the purpose is unambiguous.

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 is provided on when to use this tool versus alternatives. It doesn't mention prerequisites, timing, or comparisons to sibling tools like 'get_aave_reserves' for reserve data or 'get_user_health' for user-specific status.

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