Skip to main content
Glama

Get DEX pulse

get_dex_pulse
Read-onlyIdempotent

Educational DefiLlama DEX pulse: the five largest Dexs-category protocols by reported TVL and volume (size order, not a ranking), plus overview 24h volume and a methodology block. Not prices, not a trade ranking, not a swap. Education only, not financial advice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
asOfYes
marketYes
sourceYes
topTvlYes
disclaimerYes
topVolume7dYes
topVolume24hYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / topTvl / items / properties / change1dPct
      Removed value: -{
      -  "type": [
      -    "number",
      -    "null"
      -  ]
      -}
    • removedOutput schema / properties / topVolume24h / items / properties / change1dPct
      Removed value: -{
      -  "type": [
      -    "number",
      -    "null"
      -  ]
      -}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "asOf": {
      +      "type": "string"
      +    },
      +    "disclaimer": {
      +      "type": "string"
      +    },
      +    "market": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "volume24hUsd": {
      +          "type": "number"
      +        },
      +        "volume7dUsd": {
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "volume24hUsd",
      +        "volume7dUsd"
      +      ],
      +      "type": "object"
      +    },
      +    "schema_version": {
      +      "type": "string"
      +    },
      +    "source": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "name": {
      +          "type": "string"
      +        },
      +        "urls": {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        }
      +      },
      +      "required": [
      +        "name",
      +        "urls"
      +      ],
      +      "type": "object"
      +    },
      +    "topTvl": {
      +      "items": {
      +        "additionalProperties": true,
      +        "properties": {
      +          "chains": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "change1dPct": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "rank": {
      +            "type": "integer"
      +          },
      +          "slug": {
      +            "type": "string"
      +          },
      +          "tvlUsd": {
      +            "type": "number"
      +          }
      +        },
      +        "required": [
      +          "rank",
      +          "name",
      +          "tvlUsd"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "topVolume24h": {
      +      "items": {
      +        "additionalProperties": true,
      +        "properties": {
      +          "change1dPct": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "rank": {
      +            "type": "integer"
      +          },
      +          "volume24hUsd": {
      +            "type": "number"
      +          },
      +          "volume7dUsd": {
      +            "type": "number"
      +          }
      +        },
      +        "required": [
      +          "rank",
      +          "name",
      +          "volume24hUsd"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "topVolume7d": {
      +      "items": {
      +        "additionalProperties": true,
      +        "properties": {
      +          "name": {
      +            "type": "string"
      +          },
      +          "rank": {
      +            "type": "integer"
      +          },
      +          "volume24hUsd": {
      +            "type": "number"
      +          },
      +          "volume7dUsd": {
      +            "type": "number"
      +          }
      +        },
      +        "required": [
      +          "rank",
      +          "name",
      +          "volume7dUsd"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "schema_version",
      +    "asOf",
      +    "source",
      +    "disclaimer",
      +    "market",
      +    "topTvl",
      +    "topVolume24h",
      +    "topVolume7d"
      +  ],
      +  "type": "object"
      +}
  3. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description still adds real interpretive context beyond that: the ordering is by size rather than a ranking, TVL figures are 'reported', and each response carries a methodology block — all of which affect how results should be presented. It does not discuss freshness/caching or data staleness, which keeps it short of a 5.

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?

The payload is front-loaded in a single dense sentence that leads with what the tool returns before the caveats. The closing negation and disclaimer clauses are slightly repetitive ('not a trade ranking, not a swap' plus 'Education only, not financial advice'), but each tier still earns its place as a misuse guard.

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 zero-parameter read-only tool, the description covers the returned entities, their ordering semantics, the presence of a methodology block, and the educational framing. With an output schema present it need not spell out field-level return values, so nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The absence of inputs is consistent with the description presenting a fixed-shape pulse response.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource (an 'Educational DefiLlama DEX pulse') and enumerates exactly what it returns: the five largest Dexs-category protocols by reported TVL and volume plus overview 24h volume and a methodology block. The negation chain ('not prices, not a trade ranking, not a swap') further separates it from trading-oriented tools, so an agent can tell what this is without opening the output schema.

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

Usage Guidelines4/5

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

It gives explicit when-not-to-use signals ('not prices, not a trade ranking, not a swap') and a scope caveat ('size order, not a ranking'), which steers the agent away from misusing it for price or ranking queries. The gap is that it never states the positive trigger ('use when the user asks about aggregate DEX TVL/volume'), and it names no alternative sibling for those adjacent needs.

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