Skip to main content
Glama

FoxAPIs data sources

DefiLlama protocol

defillama_protocol
Read-onlyIdempotent

Total value locked and chain breakdown for a DeFi protocol, by name. Costs 5 credits a call; an answer with no data is not charged. Needs your FoxAPIs key (free to start).

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": {
      "protocol": "<protocol>"
    },
    "name": "defillama_protocol"
  }
}

Input Schema

NameRequiredDescriptionDefault
protocolYesFor example: "aave"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuinely new operational context: a 5-credit per-call cost, a no-charge guarantee for empty results, and an API-key requirement. Only the response shape and failure modes beyond 'no data' are left implicit.

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 short sentences: what it returns, what it costs, what it needs. Zero padding and the core capability is front-loaded before the commercial/credential details.

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 still tells the agent the payload content (TVL plus per-chain breakdown), which is the essential return-value information. Cost, billing edge case, and auth prerequisites make it callable without surprises; only pagination/units/error behavior remain unstated for a one-parameter tool.

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 coverage is 100% and the single parameter already carries an example ("aave"), so the schema does the heavy lifting. 'By name' in the description only loosely corroborates the expected identifier form and adds no syntax, casing, or slug-format detail beyond the schema.

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 concrete verb+resource pair: 'Total value locked and chain breakdown for a DeFi protocol, by name.' An agent knows exactly what data comes back and what input shape is expected. It does not differentiate itself from a near-tool like coingecko_coin, which is the only meaningful gap.

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?

Usage is implied by 'for a DeFi protocol, by name' — the agent can infer it is the tool to reach for when it has a protocol slug. There is no explicit when-to-use/when-not guidance, no statement of what to do if the protocol is unknown, and no named alternative for token-level or price data.

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