Coil Live

get_crypto_trend

Read-onlyIdempotent

Are Bitcoin and Ethereum in an uptrend? The same gate for crypto: whether BTC and ETH are in an uptrend or in cash. Bitcoin and Ethereum trend signal: the long-only state for each sleeve (LONG or CASH), the 50-day trend gate each trades on, and the BTC 200-day master gate that overrides both, evaluated on UTC daily closes with price and day change. A rules-based risk-on/risk-off verdict for crypto, not raw price data. Free; exactly one completed UTC close behind, evaluated every calendar day including weekends and stamped with the close used (signal_close_date).

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": "get_crypto_trend"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 25, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the read-only/idempotent annotations, it discloses that the signal is free, lagged by exactly one completed UTC close, evaluated every calendar day including weekends, and stamped with signal_close_date. That is exactly the behavioral context an agent needs to trust and time the result.

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

Conciseness3/5

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

The opening question front-loads the purpose well, but the following sentences restate the same uptrend-or-cash idea multiple times and are long and clause-heavy. It is informative but not tight; some repetition could be removed without losing meaning.

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?

There is no output schema, yet the description enumerates the key returned concepts: per-sleeve LONG/CASH state, the 50-day gate, the overriding BTC 200-day master gate, price and day change, and signal_close_date. For a zero-parameter, read-only signal tool, that is sufficient completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so there is nothing for the description to disambiguate beyond the meaning of the returned signal. The schema is empty and the description correctly focuses on outputs rather than inventing parameter semantics.

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?

The description names the specific resource (Bitcoin and Ethereum trend state), the exact outputs (LONG/CASH per sleeve, 50-day gate, BTC 200-day master gate, price and day change), and the evaluation basis (UTC daily closes). It is clearly distinct from raw crypto price tools and from the *_live siblings by stating it is exactly one completed UTC close behind.

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?

It makes the use case clear: a rules-based risk-on/risk-off verdict rather than raw price data, and it explains the freshness trade-off versus a live version. It does not explicitly name get_crypto_trend_live as the alternative, so the routing guidance is strong but not fully explicit.

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

All Coil Live 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?