Skip to main content
Glama
CantorFi MCP server

CantorFi MCP server

Official
by cantorfi

Run the CantorFi liquidation bot

cantorfi_liquidation_bot
Read-onlyIdempotent

Run an open-source liquidation bot read-only without a key, or liquidate with your own wallet; retrieve the repository and network-filled commands.

Instructions

How to run the open-source CantorFi liquidation bot: read-only without a key, or liquidating with the user's own wallet. Returns the repository and the commands filled with the network values.

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": "cantorfi_liquidation_bot"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered; the description adds that no key is needed for read-only use and that the output is a repository plus commands already populated with network values. This is meaningful context beyond the annotations. It stops short of saying whether the repository location is fixed or network-dependent and gives no risk caveat for the liquidating mode.

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, no filler, and the read-only-versus-liquidating distinction is front-loaded before the return-value note. Every clause carries information an agent needs.

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 zero-argument informational tool with no output schema and safety already covered by annotations, the description says enough: it names both usage modes and what comes back. A little more on the shape of the returned commands and which networks are supported would make it fully self-sufficient.

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 takes zero parameters, so the baseline is 4 and there is nothing for the description to compensate for. The mention of 'network values' being filled in hints that context comes from somewhere other than arguments, which is helpful but not required.

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 states a specific subject and outcome: it returns the CantorFi liquidation bot's repository plus ready-to-run commands, in two modes. An agent knows it is getting setup material rather than an execution endpoint. It does not differentiate itself from siblings like cantorfi_contracts or cantorfi_vault, and the 'Run the bot' title is slightly at odds with a tool that only returns instructions.

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?

Two modes are named (read-only without a key, liquidating with the user's own wallet), which implicitly tells the agent the tool serves both inspection and live-liquidation setup. However there is no explicit statement of when to pick this over the sibling deployment/vault tools, and no prerequisites such as which network values are required.

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