Skip to main content
Glama

Defi Protocol Detail

defi_protocol_detail
Read-onlyIdempotent

Get detailed metrics for a specific DeFi protocol including TVL history over time, breakdown by blockchain, and token information.

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

Input Schema

NameRequiredDescriptionDefault
protocolYesProtocol slug (e.g., "aave", "uniswap", "lido", "makerdao")

Output Schema

NameRequiredDescriptionDefault
urlNoOfficial protocol URL
mcapNoMarket capitalization in USD
nameYesProtocol name
slugNoProtocol slug identifier
chainNoPrimary blockchain
chainsYesList of supported chains
symbolNoToken symbol
categoryNoProtocol category
chain_tvlsNoTVL breakdown by blockchain
current_tvlNoCurrent total value locked in USD
descriptionNoProtocol description
tvl_history_last_30YesLast 30 days of TVL history

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / required
      Previous value: -[
      -  "name",
      -  "slug",
      -  "chains",
      -  "tvl_history_last_30"
      -]New value: +[
      +  "name",
      +  "chains",
      +  "tvl_history_last_30"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "category": {
      +      "description": "Protocol category",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "chain": {
      +      "description": "Primary blockchain",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "chain_tvls": {
      +      "additionalProperties": {
      +        "type": "number"
      +      },
      +      "description": "TVL breakdown by blockchain",
      +      "type": "object"
      +    },
      +    "chains": {
      +      "description": "List of supported chains",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "current_tvl": {
      +      "description": "Current total value locked in USD",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "description": {
      +      "description": "Protocol description",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "mcap": {
      +      "description": "Market capitalization in USD",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "name": {
      +      "description": "Protocol name",
      +      "type": "string"
      +    },
      +    "slug": {
      +      "description": "Protocol slug identifier",
      +      "type": "string"
      +    },
      +    "symbol": {
      +      "description": "Token symbol",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "tvl_history_last_30": {
      +      "description": "Last 30 days of TVL history",
      +      "items": {
      +        "properties": {
      +          "date": {
      +            "description": "ISO date (YYYY-MM-DD)",
      +            "type": "string"
      +          },
      +          "tvl": {
      +            "description": "TVL value in USD",
      +            "type": "number"
      +          }
      +        },
      +        "required": [
      +          "date",
      +          "tvl"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "url": {
      +      "description": "Official protocol URL",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "name",
      +    "slug",
      +    "chains",
      +    "tvl_history_last_30"
      +  ],
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "protocol": "aave"
      +  },
      +  {
      +    "protocol": "uniswap"
      +  }
      +]
  4. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare the key safety profile: read-only, idempotent, open-world, and non-destructive. The description adds useful scope about which data categories are returned, but it does not add operational details such as rate limits, authentication needs, or handling of unknown protocol slugs.

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 a single front-loaded sentence with no wasted wording. It states the action, resource, and main data categories efficiently.

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 one-parameter read-only tool with rich annotations and an output schema, the description is largely complete. It covers the purpose and returned data categories, though it leaves alternative-tool routing 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%, and the single protocol parameter is already documented with examples in the schema. The description adds no parameter-specific meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 detailed metrics for a specific DeFi protocol. It also names the included data types (TVL history, blockchain breakdown, token information), though it does not explicitly distinguish itself from sibling tools such as defi_chain_tvl or defi_protocol_fees.

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 only implied by the purpose: use this when detailed metrics for one DeFi protocol are needed. The description gives no explicit when-to-use guidance, exclusions, or alternatives to sibling tools.

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.