Skip to main content
Glama

MCPFax Macro & Market Intelligence

by com.mcpscores
OverviewDiscussionsAdmin

DeFi protocols by TVL

defi_protocols
Read-onlyIdempotent

Rank DeFi protocols by total value locked from DefiLlama, filtered by chain, category or name substring, with each protocol's slug, category, chain list, TVL in USD, 1d/7d TVL change and market cap. Use it to size a protocol, find the biggest venues on a chain, or resolve the slug the protocol-detail tool needs. A protocol DefiLlama publishes no TVL for keeps a null figure, never a zero. Read live at request time and held for 5 minutes. Costs $0.008 USDC per call via x402 on Base; an unpaid call returns the payment challenge instead of data, and a call that returns no data is never settled so it costs nothing. Equivalent HTTP route: GET /defi/protocols.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNoOnly protocols deployed on this chain Example: 'Base'.
limitNoHow many to return, 1-100 (default 20) Example: '20'.
searchNoName or slug substring Example: 'aave'.
categoryNoExact DefiLlama category Example: 'Lending'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / category / examples
      Added value: +[
+  "Lending"
+]
    • addedInput schema / properties / chain / examples
      Added value: +[
+  "Base"
+]
    • addedInput schema / properties / limit / examples
      Added value: +[
+  20
+]
    • addedInput schema / properties / search / examples
      Added value: +[
+  "aave"
+]
  2. First observed

TDQS

A5/5.0
Behavior5/5

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

Discloses read-only, idempotent nature via annotations and additionally explains payment behavior (cost, unpaid call challenge, no settlement on no data) and data freshness (live, 5-minute hold), going beyond annotations.

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 description is well-organized, with each sentence adding value (purpose, output, usage, cost, freshness, HTTP route). No redundant fluff; it is concise yet comprehensive.

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?

Covers all necessary context: functionality, filters, output fields, use cases, payment model, data freshness, and equivalent HTTP route. Even without an output schema, the listed fields make it complete.

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

Parameters5/5

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

All 4 parameters have descriptions in the schema, and the tool description reinforces their meaning (e.g., filters by chain, category, name substring). Schema coverage is 100%, and each parameter is self-explanatory.

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?

Clearly states the tool ranks DeFi protocols by TVL from DefiLlama with filters and lists output fields. It also explicitly mentions use cases like sizing a protocol, finding biggest venues, and resolving slugs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit use cases and contrasts with the protocol-detail tool by mentioning it resolves slugs needed by that tool. Also includes cost and HTTP route, which helps decide when to use.

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

All MCPFax Macro & Market Intelligence toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources