Skip to main content
Glama

Lending rates

lending_rates
Read-only

Compare lending and borrowing rates across Solana DeFi protocols (Kamino, MarginFi, Drift, Solend, Save, Mango). Returns supply APY, borrow APY, utilization rates, reward APY, and per-asset summaries showing the best rates. Filter by asset (USDC, SOL, mSOL, etc.) or protocol. Costs $0.005 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault
assetNoFilter by asset symbol (e.g. 'USDC', 'SOL', 'mSOL', 'JitoSOL'). Omit for all assets.
protocolNoFilter by protocol (e.g. 'kamino', 'marginfi', 'drift', 'solend'). Omit for all protocols.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely non-obvious context beyond them: the $0.005 USDC per-call cost and the exact set of aggregates returned. Rate limits and freshness/staleness of the APY data are still unstated, which keeps it short of a 5.

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?

Three sentences, fully front-loaded with purpose and scope before the filter and cost details; every clause carries information an agent needs (protocol list, return fields, filter options, price). No filler or restatement of the title.

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?

With no output schema, the description correctly compensates by naming the return fields (supply APY, borrow APY, utilization, reward APY, per-asset summaries). The remaining gap is that it doesn't say whether covering all six protocols is uniform per asset or how large the response is, but an agent can call it correctly from what is given.

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 both parameters are optional with examples already documented in the schema, so the description's "filter by asset or protocol" line adds no syntax or format detail beyond it. Baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Compare lending and borrowing rates") plus the exact venue set (Kamino, MarginFi, Drift, Solend, Save, Mango), which separates it from generic siblings like yield_rates or l2_yield_scanner. It also enumerates the returned metrics and the supported filters, so the agent knows the scope without opening the schema.

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?

The description gives filtering guidance ("Filter by asset ... or protocol") and a cost caveat, which implies the intended call pattern, but it never states when to prefer this over a close sibling such as yield_rates or lst_yields, nor any exclusions. Usage is inferable rather than explicit.

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.

Resources