Skip to main content
Glama

DeFi Capital Flow-Price Gap

All tokens today (paid, x402)

get_signal
Read-only

All 10 DeFi tokens on Ethereum, daily: first-party on-chain protocol TVL inflow/outflow (not resold) vs price gap; tiers + reasons. Bitcoin-timestamped; free proof: /verify/index.json. Informational, not investment advice. Track record per tier (A/B/C, rules fixed in advance and Bitcoin-timestamped) in every response; predictive power not yet proven live. Paid: $0.01 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/signal.

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

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

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnly, non-destructive, closed-world), the description discloses the payment mechanism and channel, that no charge occurs on a payment-required response, data provenance (first-party on-chain, not resold), timestamping, and that a per-tier track record ships in every response. These are exactly the behavioral facts an agent cannot infer from the structured fields.

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 what the tool returns, then payment behavior, then caveats — a sensible order with no filler sentences. It is dense and clause-heavy (semicolons, parentheticals like 'not resold'), which costs a little readability.

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?

There is no output schema, so the description carries the burden of describing returns, and it does so at a high level: tiers plus reasons, per-tier track record in every response, and parity with GET /v1/signal. The concrete field layout of that JSON is not enumerated, but an agent has enough to decide whether to pay and call.

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 description coverage is 100% and the single receipt parameter is fully documented in the schema, including its pattern and its 'same data again without payment' meaning. The description adds nothing further about receipt handling, so the baseline of 3 applies.

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 the exact resource and scope: daily TVL inflow/outflow versus price gap for all 10 DeFi tokens on Ethereum, with tiers and reasons. 'All 10' implicitly separates it from the single-token sibling, and the 'Paid' framing separates it from free variants. It does not explicitly name a sibling to route away from, which keeps it short of a 5.

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?

Clear operational conditions: the call costs $0.01 USDC via x402 in _meta, and without payment it returns PaymentRequired and charges nothing, so an agent knows the failure mode is safe. The caveats ('informational, not investment advice', 'predictive power not yet proven live') set expectations. No explicit guidance on when to prefer the free or single-token siblings instead.

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