Toolbooth

Technical signals

technical_signals

Read-only

Technical indicators for a Solana token (by mint, or SOL/BTC/ETH) or pool, computed from the same candles as price_history: RSI(14), SMA and EMA 20/50 with their latest cross, MACD(12,26,9), ATR(14) and Bollinger Bands(20,2), each with its value and a short neutral reading of how it is conventionally interpreted (e.g. RSI above 70 is often called overbought). Descriptive only: indicators describe past prices and don't predict. Uses up to 300 candles. Fails (and is not charged) if no source has candles. Costs $0.005 USDC per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "technical_signals"
  }
}

Input Schema

Name	Required	Description
`pool`	No	A specific Solana pool address instead of the token's top pool
`token`	No	Solana token mint address, or SOL, BTC or ETH. Its most-traded pool is used
`aggregate`	No	Candles per bar: minute 1, 5 or 15; hour 1, 4 or 12; day 1 (default 1)
`timeframe`	No	Candle timeframe (default hour)

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond readOnlyHint/openWorldHint: discloses the $0.005 USDC per-call cost, that a failure with no candle source is not charged, that up to 300 candles are used, and that the output is descriptive only and not predictive. Pricing and failure-billing semantics are exactly the kind of context annotations cannot carry.

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?

Purpose is front-loaded in the first clause, followed by output contents, caveats, and cost in a logical order with no filler. The opening sentence is dense with parenthetical indicator parameters, but each detail is load-bearing for a signals tool.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by stating that each indicator comes with its value plus a short neutral interpretation, so an agent knows what it will receive. Combined with the failure/billing notes and candle limit, nothing needed to call it correctly is missing.

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 all four parameters (pool, token, aggregate, timeframe) are already documented in the schema. The description only reinforces the token/pool choice and the 300-candle cap; it adds no semantics for aggregate or timeframe beyond what the schema says, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource (technical indicators for a Solana token or pool) and enumerates exactly which indicators are computed (RSI(14), SMA/EMA 20/50, MACD, ATR, Bollinger). It also ties itself to the sibling price_history by noting the indicators use the same candles, so an agent can distinguish the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives clear operating context: token mint or SOL/BTC/ETH, or a specific pool address, and notes it fails (uncharged) if no source has candles. It does not explicitly say when to prefer it over price_history or crypto_price, so usage is strong but not fully routed against alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Toolbooth tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?