Skip to main content
Glama

Racketeer Pre-Trade Checks (Solana)

trend lite

trend_lite
Read-onlyIdempotent

Quick trend check for a coin: buy, wait or avoid. Cheap polling. Price $0.003 per call via x402 (USDC on Solana or Base); 10 free calls per IP per day. 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_lite"
  }
}

Input Schema

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

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?

Goes well beyond the readOnly/idempotent/openWorld annotations by disclosing per-call cost ($0.003 via x402 in USDC on Solana or Base), a per-IP free tier of 10 calls/day, and the critical failure mode: when payment is required the tool returns x402 payment instructions instead of data. That last detail prevents an agent from misreading a payment prompt as a trend result.

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-loads the purpose and verdict in the first sentence, then packs pricing and failure behavior compactly. The closing disclaimer is minor filler but does not obscure anything.

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?

With no output schema, the description still communicates the return shape (a buy/wait/avoid verdict) and the alternative payment-instruction response, plus cost and rate limits. It leaves unclear what supporting data accompanies the verdict, but for a 'lite' polling tool that is 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?

The single 'symbol' parameter is already fully described in the schema with a pattern and example, so the description adds no syntax or format meaning beyond it. Baseline 3 applies since schema coverage is 100%.

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?

Names a specific verb and resource ('trend check for a coin') and states the output decision space (buy, wait or avoid), so an agent knows exactly what it gets back. It stops short of differentiating itself from siblings like trend_verdict or trend_batch, so an agent cannot tell why to pick this one over those from the text 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?

'Cheap polling' implies repeated/casual use and the 'lite' framing suggests a cheaper alternative exists, but the description never states when to use this versus trend_verdict or trend_batch. Usage is implied rather than directed.

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