Skip to main content
Glama

Defi Tvl Protocols

defi_tvl_protocols
Read-onlyIdempotent

Search DeFi protocols by name or category to compare their total value locked. Returns protocol name, TVL amount, blockchain, and category.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "search": "aave"
    },
    "name": "defi_tvl_protocols"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNoFilter protocols by name (case-insensitive substring match)
categoryNoFilter by category (e.g., "DEXes", "Lending", "Bridge", "CDP", "Yield")

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / oneOf
      Added value: +[
      +  {
      +    "properties": {
      +      "found": {
      +        "description": "Present and true on an answer; a miss is the found:false branch.",
      +        "enum": [
      +          true
      +        ],
      +        "type": "boolean"
      +      },
      +      "protocols": {
      +        "items": {
      +          "properties": {
      +            "category": {
      +              "description": "Protocol category (DEX, Lending, Bridge, etc.)",
      +              "type": "string"
      +            },
      +            "chain": {
      +              "description": "Primary blockchain",
      +              "type": "string"
      +            },
      +            "chains": {
      +              "description": "List of supported chains",
      +              "items": {
      +                "type": "string"
      +              },
      +              "type": "array"
      +            },
      +            "change_1d_pct": {
      +              "description": "1-day TVL change percentage",
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            },
      +            "change_7d_pct": {
      +              "description": "7-day TVL change percentage",
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            },
      +            "name": {
      +              "description": "Protocol name",
      +              "type": "string"
      +            },
      +            "slug": {
      +              "description": "Protocol slug identifier",
      +              "type": "string"
      +            },
      +            "symbol": {
      +              "description": "Token symbol if applicable",
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "tvl": {
      +              "description": "Total value locked in USD",
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            }
      +          },
      +          "required": [
      +            "name",
      +            "slug",
      +            "tvl",
      +            "chains",
      +            "category"
      +          ],
      +          "type": "object"
      +        },
      +        "type": "array"
      +      },
      +      "showing": {
      +        "description": "Number of protocols returned (max 50)",
      +        "type": "integer"
      +      },
      +      "total_matched": {
      +        "description": "Total number of protocols matching filters",
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "total_matched",
      +      "showing",
      +      "protocols"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "description": "A miss or an unavailable upstream: found:false with a reason and a hint (the shape check-found-false-schemas.mjs expects).",
      +    "properties": {
      +      "found": {
      +        "enum": [
      +          false
      +        ],
      +        "type": "boolean"
      +      }
      +    },
      +    "required": [
      +      "found"
      +    ],
      +    "type": "object"
      +  }
      +]
    • removedOutput schema / properties
      Removed value: -{
      -  "protocols": {
      -    "items": {
      -      "properties": {
      -        "category": {
      -          "description": "Protocol category (DEX, Lending, Bridge, etc.)",
      -          "type": "string"
      -        },
      -        "chain": {
      -          "description": "Primary blockchain",
      -          "type": "string"
      -        },
      -        "chains": {
      -          "description": "List of supported chains",
      -          "items": {
      -            "type": "string"
      -          },
      -          "type": "array"
      -        },
      -        "change_1d_pct": {
      -          "description": "1-day TVL change percentage",
      -          "type": [
      -            "number",
      -            "null"
      -          ]
      -        },
      -        "change_7d_pct": {
      -          "description": "7-day TVL change percentage",
      -          "type": [
      -            "number",
      -            "null"
      -          ]
      -        },
      -        "name": {
      -          "description": "Protocol name",
      -          "type": "string"
      -        },
      -        "slug": {
      -          "description": "Protocol slug identifier",
      -          "type": "string"
      -        },
      -        "symbol": {
      -          "description": "Token symbol if applicable",
      -          "type": [
      -            "string",
      -            "null"
      -          ]
      -        },
      -        "tvl": {
      -          "description": "Total value locked in USD",
      -          "type": [
      -            "number",
      -            "null"
      -          ]
      -        }
      -      },
      -      "required": [
      -        "name",
      -        "slug",
      -        "tvl",
      -        "chain",
      -        "chains",
      -        "category"
      -      ],
      -      "type": "object"
      -    },
      -    "type": "array"
      -  },
      -  "showing": {
      -    "description": "Number of protocols returned (max 50)",
      -    "type": "integer"
      -  },
      -  "total_matched": {
      -    "description": "Total number of protocols matching filters",
      -    "type": "integer"
      -  }
      -}
    • removedOutput schema / required
      Removed value: -[
      -  "total_matched",
      -  "showing",
      -  "protocols"
      -]
  2. Changed1 schema field changed
    • changedOutput schema / properties / protocols / items / properties / tvl / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "null"
      +]
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "protocols": {
      +      "items": {
      +        "properties": {
      +          "category": {
      +            "description": "Protocol category (DEX, Lending, Bridge, etc.)",
      +            "type": "string"
      +          },
      +          "chain": {
      +            "description": "Primary blockchain",
      +            "type": "string"
      +          },
      +          "chains": {
      +            "description": "List of supported chains",
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "change_1d_pct": {
      +            "description": "1-day TVL change percentage",
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "change_7d_pct": {
      +            "description": "7-day TVL change percentage",
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "name": {
      +            "description": "Protocol name",
      +            "type": "string"
      +          },
      +          "slug": {
      +            "description": "Protocol slug identifier",
      +            "type": "string"
      +          },
      +          "symbol": {
      +            "description": "Token symbol if applicable",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "tvl": {
      +            "description": "Total value locked in USD",
      +            "type": "number"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "slug",
      +          "tvl",
      +          "chain",
      +          "chains",
      +          "category"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "showing": {
      +      "description": "Number of protocols returned (max 50)",
      +      "type": "integer"
      +    },
      +    "total_matched": {
      +      "description": "Total number of protocols matching filters",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "total_matched",
      +    "showing",
      +    "protocols"
      +  ],
      +  "type": "object"
      +}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "search": "aave"
      +  },
      +  {
      +    "category": "DEXes"
      +  }
      +]
  5. 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, so the safety profile is covered. The description adds nothing beyond that except a restatement of return fields, which the output schema already documents; there is no mention of result limits, pagination, or ordering.

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?

Two short sentences, front-loaded with the action and resource, with zero filler. The second sentence is somewhat redundant given an output schema exists, but the text remains tight and easy to scan.

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 simple two-parameter, zero-required search tool with full schema coverage, complete annotations, and an output schema, the description is sufficient to call the tool correctly. Only minor gaps remain around result ordering and how the two filters interact.

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%, so both parameters are already fully documented including case-insensitive substring matching and example categories. The description only restates "by name or category" and adds no new semantics such as whether filters combine with AND or what an empty result means.

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?

States a specific verb+resource ("Search DeFi protocols") with the scope of the search (by name or category) and the metric involved (total value locked). This distinguishes it from siblings like defi_chain_tvl or defi_protocol_detail, though it never names an alternative explicitly.

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 phrase "to compare their total value locked" implies a comparison use case, but there is no explicit when-to-use or when-not guidance, no mention of when to prefer defi_chain_tvl or defi_protocol_detail, and no note on combining or omitting filters.

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.