truss44-mcp-crypto-price

Get Candlestick Data

analysis-candlestick

Read-onlyIdempotent

Get OHLCV candlestick data for a cryptocurrency. Useful for charting and technical analysis.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No	Number of days of candlestick data to retrieve (1-30)
`symbol`	Yes	Cryptocurrency symbol or name (e.g. BTC or Bitcoin)
`interval`	No	Candle interval: m5=5min, m15=15min, m30=30min, h1=1hr, h2=2hr, h6=6hr, h12=12hr, d1=daily	h1

Output Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`symbol`	Yes
`candles`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 10, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed12 schema fields changedJul 2, 2026

removedInput schema / properties / exchange

Removed value: -{
-  "default": "poloniex",
-  "description": "Exchange ID (e.g. \"poloniex\", \"bittrex\", \"kraken\", \"binance\")",
-  "type": "string"
-}

removedInput schema / properties / quote

Removed value: -{
-  "default": "usd",
-  "description": "Quote currency ID (e.g. \"usd\", \"usdt\", \"btc\")",
-  "type": "string"
-}

changedOutput schema / properties / candles / items / properties / close / type
```
Previous value: -"string"New value: +"number"
```
changedOutput schema / properties / candles / items / properties / high / type
```
Previous value: -"string"New value: +"number"
```
changedOutput schema / properties / candles / items / properties / low / type
```
Previous value: -"string"New value: +"number"
```
changedOutput schema / properties / candles / items / properties / open / type
```
Previous value: -"string"New value: +"number"
```
removedOutput schema / properties / candles / items / properties / period
```
Removed value: -{
-  "type": "number"
-}
```
addedOutput schema / properties / candles / items / properties / time
```
Added value: +{
+  "type": "number"
+}
```
removedOutput schema / properties / candles / items / properties / volume
```
Removed value: -{
-  "type": "string"
-}
```

changedOutput schema / properties / candles / items / required

Previous value: -[
-  "open",
-  "high",
-  "low",
-  "close",
-  "volume",
-  "period"
-]New value: +[
+  "open",
+  "high",
+  "low",
+  "close",
+  "time"
+]

removedOutput schema / properties / exchange
```
Removed value: -{
-  "type": "string"
-}
```

changedOutput schema / required

Previous value: -[
-  "name",
-  "symbol",
-  "exchange",
-  "candles"
-]New value: +[
+  "name",
+  "symbol",
+  "candles"
+]

AddedJul 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already cover the read-only, idempotent, and non-destructive nature of the tool. The description adds no additional behavioral context such as pagination, rate limits, or data format. It does not contradict annotations, but also does not enrich them beyond the basic action.

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?

The description is a single sentence that is direct and front-loaded with the core action. It includes a brief usage note without unnecessary fluff, making it appropriately concise.

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 simple tool with fully documented parameters and an output schema, the description provides sufficient context for an agent to understand what the tool does and when it is useful. It could arguably mention the range of days or intervals, but these are in the schema, so the description is complete enough.

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?

All three parameters have descriptions in the schema (100% coverage), so the description does not need to add parameter semantics. The description itself does not mention any parameters, which is acceptable given the high schema coverage.

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 clearly states the tool retrieves OHLCV candlestick data for cryptocurrencies, a specific verb and resource. It also notes utility for charting and technical analysis. However, it does not explicitly differentiate from sibling tools like analysis-historical or analysis-technical, though the candlestick focus is distinctive.

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 description gives a usage context ('useful for charting and technical analysis') but does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention exclusions or when not to use it. This is implied rather than explicit.

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

All truss44-mcp-crypto-price 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.