Skip to main content
Glama

DeFi Capital Flow-Price Gap

Asset-level inflow today (paid, x402)

get_inflow_assets
Read-only

Asset-level protocol TVL inflow/outflow for 10 DeFi tokens on Ethereum: first-party on-chain reads at a fixed daily block. Bitcoin-timestamped; free proof: /verify/index.json. Informational, not investment advice. Paid: $0.02 USDC on Base with x402 inside the MCP call (_meta["x402/payment"]); without payment the tool returns the x402 PaymentRequired result and nothing is charged. Same JSON as GET /v1/inflow/assets.

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_inflow_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
receiptNooptional: refetch.receipt from an earlier paid answer of the same tool - the same data again without payment (terms 2b)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses the exact price ($0.02 USDC on Base), the x402 payment channel (_meta["x402/payment"]), and that an unpaid call is a no-charge no-op returning PaymentRequired. It also notes Bitcoin timestamping, a free proof artifact, and an informational-only disclaimer — all behavior an agent could not infer from readOnlyHint/destructiveHint alone.

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-loads what the tool returns, then the payment mechanics, then the proof pointer — a sensible order with no filler sentences. It is dense, but every clause (price, fallback behavior, receipt reuse) carries operational weight.

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 compensates by naming the exact REST equivalent ('Same JSON as GET /v1/inflow/assets') and describing the payment/retry lifecycle. It stops short of characterizing the response fields or the daily-block window, so an agent still needs the external endpoint docs to interpret results.

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%, so the single optional 'receipt' parameter is fully documented with its pattern and terms reference; the description adds nothing about it beyond the schema. Baseline 3 applies since the schema carries the parameter burden.

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?

Names a specific resource and scope: 'Asset-level protocol TVL inflow/outflow for 10 DeFi tokens on Ethereum', plus the provenance ('first-party on-chain reads at a fixed daily block'). An agent knows exactly what data comes back, but the description never contrasts this with siblings such as get_token_signal or get_signal, so differentiation is left implicit.

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?

It states the payment precondition and the fallback (returns PaymentRequired, nothing charged) and that a receipt from a prior paid answer can be reused, which is genuine use guidance. It does not say when to prefer this asset-level tool over the token-level or free-signal siblings, so routing guidance is only implied.

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