Skip to main content
Glama

CantorFi isolated lending vaults

Search CantorFi

search
Read-onlyIdempotent

Search CantorFi vaults and guides (isolated lending, liquidations, prediction market settlement, B20 tokens, ERC-4626); returns ids for fetch.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so safety is covered. The description adds real behavioral context beyond that: the searchable corpus (vaults and guides, with named domains) and the shape of the result (ids rather than full records), which materially shapes how an agent plans its next call. It omits ranking, result caps, and pagination behavior.

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 sentence with the resource and the payoff ('returns ids for fetch') front-loaded, and the parenthetical domain list is compact. The dense parenthetical slightly slows scanning but every element conveys scope information an agent can use.

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 one-parameter read-only search with full annotation coverage and no output schema, the description supplies the essentials: corpus scope and return shape. The remaining gaps (query syntax, result limits) are modest but real for a tool whose only input is a free-form string.

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

Parameters2/5

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

There is one parameter (query) with a type-only schema at 0% description coverage, so the description must carry the burden. The enumerated domains hint at acceptable query topics, but nothing is said about whether query is natural language, keywords, ids, or filters, leaving the agent to guess at input form.

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 pairs a specific verb (Search) with a specific resource (CantorFi vaults and guides) and enumerates the covered domains, so an agent knows the index scope. It also distinguishes itself from the sibling 'fetch' by stating it returns ids for fetch, though it does not differentiate itself from cantorfi_vault/cantorfi_vaults/contracts 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?

Usage is implied rather than stated: 'returns ids for fetch' signals a two-step search-then-fetch workflow, which is genuinely useful routing guidance. However, there is no explicit when-to-use/when-not guidance and no statement about whether this is the entry point for every CantorFi lookup versus a domain-specific alternative.

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.