Skip to main content
Glama

FinanceQuery

DeFi Protocol TVL History

get_protocol_tvl_history
Read-onlyIdempotent

Get a DeFi protocol's TVL history, oldest first (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_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCoinGecko coin id (e.g. aave)
limitNoMaximum entries per page; omitted = curated default (25)
cursorNoOpaque continuation token from a previous response's `pageInfo.endCursor`; omitted = first page
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
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety and repeatability are covered structurally. The description adds genuinely new facts beyond that — the upstream source (DefiLlama), that it is keyless (no auth required), and the chronological ordering of results — but says nothing about rate limits, pagination behavior, or what a data point contains.

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 front-loaded sentence with no filler; the ordering and source/auth facts are packed in without waste. The parenthetical stacks two unrelated facts (source, auth) and slightly crowds the sentence, but nothing is superfluous.

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?

For a read-only, paginated history endpoint with full schema coverage and no output schema, the description covers what matters most: what data is returned, in what order, from which source, and that no key is needed. Remaining details such as page size defaults and field selection live in the schema, so nothing essential is missing.

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 id, limit, cursor, and fields are all documented in the schema, including the cursor's origin from pageInfo.endCursor. The description adds no parameter meaning of its own beyond noting the source, which makes the baseline 3 correct.

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 states a specific verb and resource ("Get a DeFi protocol's TVL history") and adds the ordering guarantee "oldest first," which distinguishes it from a snapshot-style TVL tool. It never names the sibling get_protocol_tvl, so the contrast is implied rather than explicit.

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 "TVL history, oldest first" implies this is the tool for a time series rather than a current-value lookup, which is useful context. There is no explicit when-to-use or when-not-to-use guidance and no named alternative, so the agent must infer the boundary from the sibling list.

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.