Skip to main content
Glama

FinanceQuery

DeFi Protocol TVL

get_protocol_tvl
Read-onlyIdempotent

Get a DeFi protocol's total value locked and per-chain split (DefiLlama, keyless).

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": {
      "id": "<id>"
    },
    "name": "get_protocol_tvl"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCoinGecko coin id (e.g. aave)
fieldsNoComma-separated list of GraphQL field names to include; omitted = all fields

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real value beyond the annotations: the upstream source (DefiLlama) and that the call is keyless (no auth/credentials required), which affects how an agent plans the call. It doesn't disclose error or not-found behavior, keeping it out of 5 territory.

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?

A single sentence with no filler, leading with the verb and the core resource before the parenthetical provenance. Every clause carries information. Nothing to trim.

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 two-parameter read tool with full schema coverage, complete annotations and no output schema, this is nearly enough to call correctly. The remaining gap is that the 'fields' parameter is a GraphQL field selector that the description never acknowledges, and failure behavior for an unknown protocol id is unstated.

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 documented and a baseline of 3 applies. The description adds no format or semantics detail for either parameter. If anything, it introduces mild friction by naming DefiLlama while the schema asks for a 'CoinGecko coin id', which the description does not reconcile.

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 names a specific verb ('Get'), resource ('a DeFi protocol's total value locked') and scope ('per-chain split'), plus the data source and that no key is needed. That is far more informative than the title alone. It doesn't explicitly distinguish itself from the sibling get_protocol_tvl_history, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative, even though get_protocol_tvl_history is an obvious sibling an agent must choose between. The 'keyless' note gives a small auth-related hint but is not usage guidance. Current-vs-historical selection is left entirely to inference.

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.