Atomadic MCP

Defi Liquidation Check

defi_liquidation_check

Read-onlyIdempotent

[defi] Liquid Shield (LQS-100-LiquidationBound)

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": {
      "position_id": "<position_id>",
      "collateral_value": "<collateral_value>",
      "debt_value": "<debt_value>",
      "collateral_factor": "<collateral_factor>"
    },
    "name": "defi_liquidation_check"
  }
}

Input Schema

Name	Required	Description	Default
`debt_value`	Yes
`position_id`	Yes
`collateral_value`	Yes
`collateral_factor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

D1/5.0

Behavior1/5

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

The annotations already provide comprehensive behavioral context (readOnlyHint: true, destructiveHint: false, idempotentHint: true). The description adds zero unique behavioral information.

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

Conciseness1/5

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

While extremely short, the definition is structured like metadata rather than helpful documentation. It is not concisely functional.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having a complex input schema with four specific financial metrics, the definition provides no context whatsoever on what the tool calculates or returns. It is maximally incomplete.

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

Parameters1/5

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

Schema description coverage is 0%, and the description provides no guidance or context for the four required parameters, failing to compensate for the lack of structured documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description only contains a source identifier ('Liquid Shield (LQS-100-LiquidationBound)') and does not state what the tool actually does beyond its title.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There are no instructions provided on when or how to use this tool relative to other available functions or scenarios.

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

All Atomadic MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?