MetaVault MCP

spectra_get_pool_volume

Retrieves historical trading volume and volume/liquidity ratio for any Spectra pool, helping assess market activity and liquidity depth before entering a position.

Instructions

Get historical trading volume for a specific Spectra pool. Returns timestamped buy/sell volume in USD. Use spectra_list_pools first to find pool addresses. Useful for assessing pool activity and liquidity depth before entering a position.

Context: Volume alone doesn't indicate capital efficiency — $1M volume in a $5M liquidity pool is very different from $1M in a $500K pool. Combine volume data with pool liquidity (from spectra_list_pools or spectra_get_pt_details) to assess real trading conditions.

Output includes volume/liquidity ratio analysis when pool data is available. For individual transaction details and whale activity, use spectra_get_pool_activity instead. Use spectra_quote_trade to estimate price impact for a specific trade size.

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": {
      "chain": "<chain>",
      "pool_address": "<pool_address>"
    },
    "name": "spectra_get_pool_volume"
  }
}

Input Schema

Name	Required	Description	Default
`chain`	Yes	The blockchain network
`pool_address`	Yes	The Curve pool address (0x...) OR a PT address. If a PT address is given, it will be resolved to the corresponding pool automatically.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0May 27, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations provided, so description carries full burden. It discloses that output includes timestamped buy/sell volume in USD and optionally a volume/liquidity ratio when pool data is available. Lacks details on data range, pagination, or caching, but for a read tool it is reasonably transparent.

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 concise at about 130 words, well-structured with the purpose first, then output, usage tips, context note, and alternatives. Every sentence adds value with no redundancy.

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?

Given no output schema or annotations, the description effectively covers the tool's purpose, usage, and integration with other tools. It explains the return value and provides important context about using volume with liquidity. Minor gaps like missing time range or pagination, but overall very complete for a 2-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?

Input schema coverage is 100% with clear descriptions for both parameters. The description does not add significant meaning beyond what the schema provides, such as the chain enum or pool address pattern, so baseline 3 is appropriate.

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 clearly states the tool retrieves historical trading volume for a specific Spectra pool, returning timestamped buy/sell volume in USD. It differentiates from siblings by explicitly mentioning volume and directing users to other tools for transaction details or price impact.

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

Usage Guidelines5/5

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

Provides explicit guidance on using spectra_list_pools first to find pool addresses, suggests combining with liquidity data from other tools, and directs users to spectra_get_pool_activity for transaction details and spectra_quote_trade for price impact, covering when to use alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server