Skip to main content
Glama
Sign In
fibx

fibx

Official
by Fibrous-Finance
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Aave V3 Account Status

get_aave_status
Read-only

Fetch Aave V3 position health on Base: health factor, total collateral, total debt, and available borrows in USD.

Instructions

Get Aave V3 position health on Base: health factor, total collateral, total debt, and available borrows in USD.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_aave_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds value by specifying the exact return data (health factor, collateral, debt, borrows), which is beyond the annotation fields. However, it does not disclose potential side effects, rate limits, or authentication requirements, though none are expected for a read-only query.

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?

A single well-structured sentence that is front-loaded with the key verb ('Get') and includes all relevant information without waste.

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?

Although no output schema exists, the description lists all returned fields. For a zero-parameter, read-only tool, this is largely complete. It could mention that it queries the connected wallet's position, but this is implied.

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 zero parameters, so schema coverage is 100%. The description need not add parameter details; the baseline score of 4 is appropriate.

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 it retrieves Aave V3 position health on Base, listing specific metrics (health factor, total collateral, total debt, available borrows in USD). This distinguishes it from sibling tools like get_aave_markets (market data) and aave_action (performing actions).

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 checking account health but does not explicitly state when to use this tool versus alternatives. No guidance on prerequisites or exclusions is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools