Skip to main content
Glama

Racketeer Pre-Trade Checks (Solana)

signal batch experimental

signal_batch_experimental
Read-onlyIdempotent

Experimental confluence scores for up to 10 coins (logged publicly at /track-record). EXPERIMENTAL: the rules-based scanner behind this has a poor hypothetical paper record so far; every served signal is logged publicly at /track-record with its outcome. Price $0.03 per call via x402 (USDC on Solana or Base). When payment is needed the tool returns x402 payment instructions instead of data. Not financial advice.

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": {
      "symbols": "<symbols>"
    },
    "name": "signal_batch_experimental"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYesComma-separated tickers, up to 10, e.g. BTC,ETH,SOL (e.g. BTC,ETH,SOL)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent, and the description adds substantial context on top: cost ($0.03 per call via x402 in USDC on Solana or Base), the payment-gate behavior (returns x402 payment instructions instead of data), and public outcome logging at /track-record. It also discloses the reliability caveat about the underlying scanner's paper record, which no annotation could convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core facts are front-loaded, but "/track-record" and the public-logging point appear twice in slightly different wording, and "Not financial advice" is boilerplate that consumes space without aiding invocation. Tightening the duplicated logging sentence would make it materially crisper.

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 single-parameter read tool with no output schema, the description covers cost, the payment-interception return path, and the reliability caveat, which is enough for an agent to call it and interpret the outcome. It does not say what the confluence score looks like or how it is scaled, but no output schema exists to carry that, leaving a minor gap.

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%, so the single symbols parameter is already fully documented by the schema's comma-separated ticker format and pattern. The description only restates the "up to 10 coins" limit, adding nothing about format or edge cases beyond what the schema provides, 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?

"Experimental confluence scores for up to 10 coins" gives a clear resource (confluence scores) and an explicit scope limit (10 coins, batch), which implicitly separates it from a single-coin sibling like signal_experimental. It stops short of naming that sibling directly, so the differentiation is inferred from context 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description warns that the scanner has a poor hypothetical paper record and points to /track-record, which is meaningful guidance on whether to trust the output. However, it never states when to choose this over signal_experimental or trend_batch, nor any preconditions beyond payment; the routing guidance is only implied by the word "batch".

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