Skip to main content
Glama
Sign In
graph-lending-mcp

graph-lending-mcp

by PaulieB14
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_liquidations

Read-only

Retrieve recent liquidation events including liquidator, liquidatee, collateral asset, and profit amounts. Optionally filter by market.

Instructions

Recent liquidation events with liquidator, liquidatee, collateral asset, and profit amounts. Optionally filter by market.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "protocol": "<protocol>"
    },
    "name": "get_liquidations"
  }
}

Input Schema

NameRequiredDescriptionDefault
firstNoNumber of events to return
networkNoNetwork filter. Use these exact values: MAINNET (Ethereum), MATIC (Polygon), ARBITRUM_ONE (Arbitrum), AVALANCHE, BASE, BSC (BNB Chain), OPTIMISM, FANTOM, GNOSIS, BLAST, SCROLL, NEAR, HARMONY, MOONBEAM, MOONRIVER, AURORA, LINEA, ZKSYNC_ERA. Omit to use the default (first) deployment.
protocolYesProtocol registry slug. Must be one of: aave-amm, aave-arc, aave-rwa, aave-v2, aave-v3, abracadabra, alpaca-finance-lending, banker-joe, bastion-protocol, benqi, burrow, compound-v2, compound-v3, cream-finance, dforce, euler-finance, geist-finance, goldfinch, inverse-finance, iron-bank, liquity, makerdao, maple-finance-v1, maple-finance-v2, moonwell, morpho-aave-v2, morpho-aave-v3, morpho-compound, notional-finance, pac-finance, qidao, radiant, rari-fuse, scream, seamless-protocol, seismic, sonne-finance, spark-lend, truefi, uwu-lend, venus, vesta-finance, zerolend
market_idNoMarket contract address to filter by (0x...). Get from get_markets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, indicating a read operation. The description adds that events are 'recent' and lists included fields, but does not disclose behavior like pagination, data freshness, or default ordering. With annotations present, the description provides minimal additional behavioral context.

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?

Two sentences, front-loaded with the tool's purpose and output fields. The second sentence covers optional filtering. No extraneous words. Conciseness is ideal.

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?

For a simple list tool with annotations and full schema coverage, the description is mostly complete. It states what is returned and the optional filter. However, it does not mention the default behavior of the 'first' parameter (returning up to 25 events) or the ordering of results, which are minor gaps given no output schema.

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% with each parameter described. The description adds only the phrase 'optionally filter by market' for market_id, which adds little beyond the schema. The baseline of 3 is appropriate as the schema already handles parameter semantics adequately.

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?

Description clearly states the tool returns recent liquidation events with specific fields (liquidator, liquidatee, collateral asset, profit amounts). The verb 'get' and resource 'liquidation events' are explicit. It distinguishes from sibling tools (e.g., get_borrows, get_deposits) by specifying the event type.

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 mentions optional filtering by market, implying use cases, but lacks explicit guidance on when to use this tool versus alternatives. No exclusions or prerequisites are provided, leaving the agent to infer from the sibling list.

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