Skip to main content
Glama

Dip signals

dip_signals

Multi-chain dip trading signals & live dip watchlist across Hyperliquid, Base, Solana, Arc and BNB Chain (excludes X1). Optional chain=all|hyperliquid|base|solana|arc|bnb. BUY at 6.5–8% below 24h high once stabilized and exit-verified, target +6.5–8%, 30d expiry; full track record included. Not advice. $0.01 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
chainNooptional: all (default), hyperliquid, base, solana, arc or bnb
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations present, the description carries the full burden and does so: it discloses cost ($0.01 per call), accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), the x402 two-step auth dance, and the exact signal logic (BUY at 6.5–8% below 24h high once stabilized and exit-verified, +6.5–8% target, 30-day expiry, track record included). It also flags 'Not advice', which is a meaningful usage caveat rather than filler.

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 it is and which chains, then cost and payment mechanics. Dense but nearly every clause carries information an agent needs. The parenthetical payment-rail list and the track-record mention are the most compressible parts, but nothing is a pure restatement of the name.

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?

No output schema exists, and the description compensates by naming the payload contents (dip signals, live watchlist, full track record). Cost, payment flow, chain scope, and signal criteria are all covered, which is everything an agent needs to decide to call it and to drive the two-step payment correctly.

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%, so the baseline is 3, but the description adds real meaning: it enumerates the accepted `chain` values with the default, and clarifies the `payment` lifecycle — that passing the signed payload makes the purchase complete within the call, rather than being a separate authorization step. The only mild friction is the 'excludes X1' claim sitting next to XNT-on-X1 payment acceptance, which could read as inconsistent.

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 states a specific resource and scope: multi-chain dip trading signals plus a live dip watchlist across five named chains, with an explicit exclusion (X1). The 'multi-chain' framing plus the chain=all default implicitly separates it from the per-chain siblings (arc_dip_signals, base_dip_signals, hl_dip_signals, etc.), though it never names them, so differentiation is inferable rather than stated.

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?

Gives a concrete invocation protocol for the paid flow: call once without `payment` to receive terms, sign with your own wallet, then call again with `payment` to complete the purchase inside the same call. Also indicates chain selection semantics with 'all' as default. It stops short of saying when to prefer this over the single-chain siblings or over the smart-signals tools.

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