Skip to main content
Glama

Volume history

volume_history
Read-only

A protocol's trading volume per day (USD) for up to 3650 days: kind dexs (spot DEX volume), options (options notional) or aggregators. The slug is a module from volumes (uniswap-v3) or an AlphaGrowth project slug. Gives the period's total and the latest day's volume on each chain; chain_history=yes adds each chain's daily series. Free data from AlphaGrowth (alphagrowth.io).

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": {
      "slug": "<slug>"
    },
    "name": "volume_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDays of daily history, counting today.
kindNodexs, options or aggregators.dexs
slugYesThe protocol's module as volumes lists it, or its project slug.
chain_historyNoyes to add each chain's daily series over the same days.no

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/non-destructive, so the description's added value is in the data contract: period total plus latest-day volume per chain, and that `chain_history=yes` extends to full daily series per chain. It also names the upstream source (AlphaGrowth) and notes the data is free, which helps an agent reason about coverage.

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?

Three dense sentences, front-loaded with what is returned and the valid `kind` values, followed by slug resolution and output variants. Slightly packed but no genuinely wasted wording.

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 does the necessary work of describing the return shape (period total, latest-day per-chain volume, optional daily series). Missing only edge behavior such as invalid-slug handling or whether chains are listed when data is absent.

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 already documents `days`, `kind`, `slug`, and `chain_history`. The description adds only modest nuance, notably that `options` means options notional rather than dollar volume, with `aggregators` left unexplained.

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?

States a specific verb and resource: a protocol's daily trading volume in USD, with the three `kind` modes enumerated and the meaning of the `slug` explained. An agent can tell this is a per-protocol volume history endpoint and how it differs from aggregate `volumes`.

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 through the `slug` explanation referencing modules 'from volumes', which hints that `volumes` is the place to discover slugs. However, it never states when to prefer this over `volumes` or `fees_history`, nor any exclusions or prerequisites.

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