Skip to main content
Glama

Racketeer Pre-Trade Checks (Solana)

trend verdict

trend_verdict
Read-onlyIdempotent

Is BTC / ETH / SOL in an uptrend? Trend check before entering a trade. 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": "trend_verdict"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, open-world behavior, yet the description adds substantial context: a per-call price of $0.01 via x402 (USDC on Solana or Base) and, critically, that the tool may return payment instructions instead of data. That conditional return path is the kind of surprise an agent needs warned about. It stops short of describing the verdict payload itself, which matters since there is no output schema.

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

Conciseness5/5

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

Four short sentences, front-loaded with the core question, then cost, then the payment fallback, then the disclaimer. Nothing is padded and each sentence carries information an agent would otherwise lack.

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 full schema coverage and no output schema, the definition covers cost, payment flow, and intended use. The remaining gap is the shape of a successful response — what a verdict actually looks like — which the absence of an output schema makes more consequential.

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% with a single required `symbol` parameter, so the schema already carries the burden and a baseline 3 applies. The description adds a mild scope signal by naming BTC/ETH/SOL, but that is in tension with the schema pattern `^[A-Za-z0-9]{2,10}$`, which accepts any ticker; it is unclear whether other tickers are supported.

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 question and resource: whether BTC/ETH/SOL is in an uptrend for a given symbol, framed as a pre-trade check. That is far more concrete than a tautology like 'trend verdict'. It does not, however, differentiate itself from the sibling tools trend_batch and trend_lite, so an agent must infer the difference from the names alone.

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?

'Trend check before entering a trade' gives a clear positive usage context. There is no when-not guidance, no mention of trend_batch for multiple symbols or trend_lite as a cheaper alternative, and no stated fallback when payment is declined.

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