Skip to main content
Glama

Base dip signals

base_dip_signals

Base DEX dip trading signals ($100k+ TVL, $50k+ vol): BUY 6.5–8% below 24h high once stabilized and verified sellable via one-block Base buy+sell simulation, target +6.5–8%, plus live dip watchlist and full track record. 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": "base_dip_signals"
  }
}

Input Schema

NameRequiredDescriptionDefault
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
Behavior4/5

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

With no annotations supplied, the description carries real weight: it discloses cost ($0.01 per call), the x402 payment rails and accepted assets, that the purchase completes inside the call, that candidates are verified sellable via a one-block buy+sell simulation, and a not-advice disclaimer. It stops short of describing what the returned payload looks like or how fresh/streamed the signals are, which is the main remaining gap.

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?

It is a single front-loaded block that leads with the offer, then terms, then the payment mechanics. It is dense and parenthetical-heavy, with pricing and the payment flow interleaved, but no sentence is filler and nothing important is buried at the end.

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?

For a one-parameter paid data tool with no output schema, the definition covers the price, payment rails, two-call flow, signal construction and validation method, and the disclaimer. The one thing an agent cannot predict is the shape of what comes back (per-signal fields, watchlist format), which matters because there is no output schema to fall back on.

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?

The single parameter is fully documented in the schema, so baseline would be 3; the description earns above that by explaining the parameter's role in a two-step protocol — omit it first to receive terms, then pass the signed x402 payload to complete the purchase. That meaning is not obvious from the schema alone.

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?

The description opens with a specific verb and resource: BUY signals on Base DEX dips of 6.5–8% below the 24h high, with entry criteria ($100k+ TVL, $50k+ vol) and a stated target. The chain scoping ('Base') plus the mention of a live watchlist and track record make it distinguishable from the arc/bnb/solana/hl sibling variants without opening any schema.

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 gives an explicit operational sequence: call once without `payment` to get terms, sign with your own wallet, call again with `payment` to complete the purchase. What is missing is any when-not-to-use routing (e.g., other-chain signals, or exit checks for positions already held), so the agent gets clear context but no explicit alternatives.

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