Skip to main content
Glama

Flow

flow
Read-onlyIdempotent

[$0.03 USD per call] Crypto ETF flow regime from settled SoSoValue data: 7- and 30-day net flows, net assets, and a falsifiable regime label (ACCUMULATING >= +$250M / DISTRIBUTING <= -$250M / FLAT). T+1 settled rows only — the newest unsettled row is excluded from sums, never counted as zero.

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": {
      "symbol": "BTC"
    },
    "name": "flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesBTC, ETH or SOL (US-listed ETFs). An unknown symbol returns 404 listing what exists.
paymentNoOptional x402 payment proof (EIP-3009 signed authorization). Call once without it to receive the payment requirements, then retry with the proof.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover safety, but the description adds billing, data source, T+1 settlement lag, exclusion of unsettled rows, and threshold rules. It does not contradict any annotation.

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?

Two dense sentences, front-loaded with cost and purpose. Every clause conveys behavior: returned metrics, thresholds, settlement handling, and billing.

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 two-parameter tool with no output schema, the description supplies return metrics, regime thresholds, data freshness, and billing. The payment protocol is fully covered by the input schema.

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 the schema already documents the symbol choices and payment retry flow. The description adds no parameter-specific semantics beyond what the high-coverage schema provides.

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 the exact resource (crypto ETF flow regime) and enumerates the returned metrics and regime thresholds, making its domain unmistakable relative to generic analytics siblings.

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?

The description implies use for crypto ETF flow regime analysis and gives data conditions, but it never states when to choose this tool over siblings or when not to use it.

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.