Skip to main content
Glama

vpin

Order-flow TOXICITY (VPIN — Volume-Synchronized Probability of Informed Trading, Easley/Lopez de Prado/O'Hara) for a token: how one-sided/informed is the recent flow? Computed via Bulk Volume Classification over 1-min candles. Returns vpin 0-1 (→1 = heavily one-sided / toxic / informed flow; →0 = balanced) and a label. The academic standard MMs/LPs use to price adverse selection — useful to size quotes, time entries, or detect informed pressure. Solana (base58) or Robinhood-chain (0x). Free 10/day, then $0.01/call.

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": {
      "token": "<token>"
    },
    "name": "vpin"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes0x-address or base58 mint

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the underlying methodology (Easley/Lopez de Prado/O'Hara BVC on 1-min candles), the value range and directional interpretation, supported chains/address formats, and a real cost/rate-limit profile (10 free/day, $0.01/call). It does not state the lookback window used for 'recent flow', nor error behavior for unknown or illiquid tokens, which are the remaining behavioral gaps.

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?

Front-loaded with the metric name, expansion, and the core question it answers, then moves to computation, output, and pricing in a logical order. The acronym expansion and academic citation are defensible for a niche metric, though 'The academic standard MMs/LPs use to price adverse selection' leans promotional rather than operational.

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 one-parameter, no-output-schema tool the description covers what is computed, how, what the return encodes (score plus label), which chains are accepted, and what it costs. The only omission, the exact time window sampled, is minor against everything else supplied.

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?

Schema coverage is 100% for the single token parameter, so baseline is 3. The description modestly adds meaning by naming the chains (Solana base58, Robinhood-chain 0x), which lets an agent map address format to ecosystem rather than treating the parameter as an opaque string.

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 specific computation (VPIN via Bulk Volume Classification over 1-min candles) on a specific resource (a token's recent order flow) and states what the output means (0-1 toxicity score plus a label). It is clear what the tool produces, but it never distinguishes itself from siblings with overlapping intent such as smart_money_flow, informed_convergence, or flow_inflection, leaving the agent to infer the boundary.

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?

Use cases are stated concretely: sizing quotes, timing entries, detecting informed pressure. Pricing context (free 10/day, then $0.01/call) helps an agent decide whether to spend a call. However, there are no exclusions and no explicit 'use X instead when Y' routing against the many sibling signal tools, so the agent gets context but not selection logic.

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