Skip to main content
Glama

DeFi Capital Flow-Price Gap

One token today (paid, x402)

get_token_signal
Read-only

One DeFi token (argument token): first-party on-chain TVL inflow/outflow vs price gap, tier + reason. All 10 tokens: /v1/signal $0.01. 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.005 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/{token}.

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": "get_token_signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYestoken symbol (the list: get_status, field token_symbols)
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.3/5.0
Behavior5/5

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

Annotations only cover read-only/idempotency; the description adds the substantive behavior: cost ($0.005 USDC on Base), payment channel (_meta["x402/payment"]), and the failure mode (x402 PaymentRequired with nothing charged). It also discloses Bitcoin timestamping, per-tier track record inclusion, and the honest caveat that predictive power is unproven — context an agent cannot get from the annotations.

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?

Purpose is front-loaded in the first clause, and every later statement (price, payment path, proof, disclaimer, return equivalence) carries information. The semicolon-chained packing of pricing, proof URL, disclaimer and track-record notes makes it denser than ideal for quick scanning.

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 does outline the return content (tier, reason, per-tier track record) and states it matches GET /v1/signal/{token}, plus explains the payment gate. It leans on an external endpoint for the exact JSON shape, which leaves a small gap for a tool that returns structured data.

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 both the token enum and the receipt refetch pattern, so the description only reinforces rather than extends that. It does clarify that token selects a single-token answer and that receipt replays a prior paid response, but adds no new format or constraint detail.

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?

Opens with a specific verb+resource pair ('One DeFi token (argument token)') and defines the output content: on-chain TVL inflow/outflow vs price gap, tier, and reason. It also implicitly separates itself from the all-tokens route ('All 10 tokens: /v1/signal $0.01'), so an agent can tell it apart from the aggregate sibling.

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?

It states the alternative route for covering all 10 tokens at a different price, and explains the receipt path for refetching the same data without payment. What's missing is an explicit instruction naming the sibling tools (e.g. get_signal, get_free_signal) and the condition that selects them, so routing is left partly to inference.

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