Skip to main content
Glama

CantorFi isolated lending vaults

CantorFi lending vaults

cantorfi_vaults
Read-onlyIdempotent

Live state of every CantorFi isolated lending vault: token, supplied, borrowed, available liquidity, utilization, borrow and supply APR, borrow limit, liquidation threshold and liquidation bonus.

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_vaults"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so the safety profile is covered. The description adds value beyond that by enumerating the returned state (supplied, borrowed, liquidity, utilization, APRs, limits, thresholds, bonus), effectively documenting the response in the absence of an output schema. It does not disclose snapshot freshness, ordering, or whether results could be large.

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 front-loaded sentence with no filler; every clause either identifies the resource, its scope, or a returned field. Nothing needs trimming or reordering.

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 no-parameter, no-output-schema read tool, the description carries the necessary burden by listing the returned metrics, which is exactly what an agent needs to decide whether one call suffices. Minor gaps remain around result size, ordering, and 'live' meaning (on-chain snapshot vs cached), which matter for an open-world tool.

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 there is no per-argument meaning to add and the baseline of 4 applies. The description correctly frames this as an unfiltered, whole-population read rather than implying hidden filters.

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 names the resource precisely (every CantorFi isolated lending vault) and the scope ('every', i.e. a full listing) plus the fields returned. A reader can distinguish it from a single-vault tool like cantorfi_vault by the plural scope, although the description never explicitly says 'list' or names the sibling alternative.

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?

Usage is only implied: 'every ... vault' suggests a broad survey rather than a single-vault lookup, which is the natural use case. There is no explicit when-to-use statement, no mention of when a caller should prefer cantorfi_vault for detail, and no prerequisites or exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.