Skip to main content
Glama

Racketeer Pre-Trade Checks (Solana)

signal experimental

signal_experimental
Read-onlyIdempotent

Experimental confluence score for a coin (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.01 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": {
      "symbol": "<symbol>"
    },
    "name": "signal_experimental"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesCoin ticker, e.g. SOL (e.g. BTC)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses the paid x402 flow, the exact price and chains, and that an unpaid call returns payment instructions instead of data. It also discloses that every served signal is logged publicly with its outcome, which is material behavior an agent could not infer from 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?

The purpose and the experimental warning are front-loaded, and most sentences earn their place by carrying pricing, payment, or logging context. The /track-record reference and the 'logged publicly with its outcome' idea appear twice, which is mild redundancy.

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 tool with no output schema, the definition covers the critical unknowns: experimental risk, per-call cost, the x402 payment response, and public logging. It does not describe the shape of the returned signal when payment succeeds, which is the main remaining 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 coverage is 100% and the single required parameter already carries a pattern and example, so the schema does the heavy lifting. The description refers to a 'coin' but adds no ticker syntax or format detail beyond what the schema provides, making the baseline 3 appropriate.

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 verb-and-resource pairing: an experimental confluence score for a coin, and it distinguishes itself from siblings through the 'EXPERIMENTAL' framing and the public track-record reference. It does not name an alternative tool such as signal_batch_experimental, but the purpose of producing a single-coin signal is clear.

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?

Usage context is implied rather than stated: an agent can infer this is the per-coin experimental signal tool and that it costs $0.01 per call. The warning about a poor hypothetical paper record functions as a caution, but there is no explicit when-to-use or when-not guidance and no routing to alternatives like signal_batch_experimental or trend_verdict.

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