Skip to main content
Glama

CantorFi isolated lending vaults

One CantorFi vault

cantorfi_vault
Read-onlyIdempotent

Live state of one CantorFi vault, chosen by token symbol (USDC, WETH), vault id or vault address.

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": {
      "vault": "<vault>"
    },
    "name": "cantorfi_vault"
  }
}

Input Schema

NameRequiredDescriptionDefault
vaultYesToken symbol, vault id or vault address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior. The description adds only that the result is live state and that identifiers can be token symbols, ids, or addresses; it does not cover freshness guarantees, error/not-found behavior, or auth requirements.

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?

The definition is a single sentence, front-loaded with the resource and scope, with no filler or redundant wording.

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

Completeness3/5

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

For a simple read-only one-parameter lookup, the description, annotations, and schema are enough to invoke the tool. However, 'live state' leaves unclear what the returned state includes, and no output schema is present to compensate for that thinness.

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 description coverage is 100% and the schema already documents the sole parameter as a token symbol, vault id, or vault address. The description adds concrete token examples (USDC, WETH), which is useful but marginal beyond the schema, so the baseline of 3 applies.

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 ('one CantorFi vault') and the retrieval intent ('live state'), and the word 'one' implicitly distinguishes it from the plural cantorfi_vaults listing sibling. It does not explicitly name or contrast with a sibling, so it falls short of the top score.

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?

It implies a targeted single-vault lookup via any accepted identifier, but it does not explicitly say when to choose this tool over cantorfi_vaults or what to do if the identifier is ambiguous. Usage is inferable but not spelled out.

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.