Skip to main content
Glama

Racketeer Pre-Trade Checks (Solana)

trend batch

trend_batch
Read-onlyIdempotent

Trend verdicts for a watchlist of up to 10 coins in one call. Price $0.02 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": "trend_batch"
  }
}

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.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world semantics, yet the description adds genuinely new behavior: a $0.02 per-call cost, x402 payment via USDC on Solana or Base, and the important fact that a payment-gated call returns payment instructions instead of data. It stops short of describing what a verdict contains or how failures other than payment gating appear.

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?

Three short sentences, front-loaded with the capability, then cost, then payment fallback. The closing 'Not financial advice' is boilerplate but brief and arguably relevant for a financial-signal tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 should convey what a 'trend verdict' actually returns, and it does not — an agent knows the cost and payment path but not the response shape. Cost, payment gating, and batch limits are otherwise well covered for a one-parameter tool.

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 symbols parameter is fully documented with a pattern and example, so the schema carries the load. The description only restates the 'up to 10 coins' limit already encoded in the regex, adding no new syntax or formatting meaning.

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?

States a specific resource (trend verdicts) and scope (a watchlist of up to 10 coins in one call), which lets an agent distinguish it from single-coin siblings like trend_verdict or trend_lite. It does not name those siblings explicitly, so the differentiation is inferable 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 phrase 'in one call' implies this is the batch path when multiple tickers are needed, but the description never says when to prefer it over trend_verdict or trend_lite, nor any exclusions. Usage is implied rather than guided.

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