Skip to main content
Glama

CantorFi isolated lending vaults

CantorFi deployed contracts

cantorfi_contracts
Read-onlyIdempotent

Network, chain id, deployment block and addresses of the CantorFi contracts: protocol registry, vault factory, reader, price oracle and every vault with its token, receipt token and staking contract.

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

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=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuine scope information beyond that: which contract families are included and that each vault arrives with its token, receipt token, and staking contract. It does not state that this is static deployment metadata (no auth, no rate limits, stable across calls), which would have completed the picture.

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

Conciseness4/5

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

A single dense sentence with no filler; the most important scope item (network/chain id/addresses) is front-loaded and the contract enumeration follows. The lack of a leading verb makes it read as a title fragment rather than an action statement, which slightly weakens the opening.

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

Completeness5/5

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

For a zero-parameter read with no output schema, the description must carry the return-value burden, and it does: it lists the network/chain fields and every contract category returned. An agent can decide whether to call it and what shape of data to expect without further documentation.

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 schema carries nothing an agent must interpret and the baseline of 4 applies. The description does not need to explain any inputs, and it correctly implies the call is parameterless by describing a fixed catalogue of deployment facts.

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 enumerates the specific resource: network, chain id, deployment block, and addresses of the CantorFi contract set (registry, vault factory, reader, price oracle, vaults with token/receipt/staking). That is concrete enough for an agent to know this is a deployment/config lookup, distinct from cantorfi_vault or cantorfi_vaults which presumably return live vault data. It stops short of an explicit verb ('returns'/'fetches') and never directly contrasts itself with the sibling tools.

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?

There is no explicit when-to-use statement, no prerequisites, and no named alternative. Usage is only implied by the content list: an agent can infer it should call this to resolve contract addresses or chain metadata. That inference is reasonable but left entirely to the reader.

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.