Skip to main content
Glama

Coil Scanner

by trade.coil

get_crypto_trend

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 tier: exactly one completed UTC close behind — evaluated every calendar day, weekends included, and stamped with the close it used (signal_close_date). Live sibling on the newest close (x402, pay-per-call): get_crypto_trend_live.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.9/5.0
Behavior5/5

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

Discloses evaluation on UTC daily closes, the exact delay (one completed close), evaluation every calendar day including weekends, and the signal_close_date stamp. Also clarifies it is rules-based rather than raw price data. With no annotations, this provides substantial transparency.

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?

Three tightly scoped sentences cover output components, evaluation cadence, delay, and live alternative without fluff; each clause adds informational value.

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?

Despite lacking output schema, the description enumerates the key output fields (LONG/CASH states, trend gates, price, day change, signal_close_date) and explains the operational context (UTC closes, calendar-day evaluation, free-tier delay), making it self-sufficient for a zero-param tool.

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?

Tool has zero parameters; empty schema with 100% coverage, so description adds no parameter semantics. Baseline 4 applies for zero-param tools.

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?

Clearly states it provides Bitcoin and Ethereum trend signals with LONG/CASH states, 50-day and 200-day gates, evaluated on UTC daily closes, and distinguishes itself from raw price data. The explicit contrast with get_crypto_trend_live differentiates it from the sibling.

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

Usage Guidelines5/5

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

Explicitly identifies the free tier's one-close lag and points to get_crypto_trend_live for the newest close, explaining the tradeoff. Clarifies it is a risk-on/risk-off verdict, not raw price data, guiding appropriate use.

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

All Coil Scanner toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0
Disambiguation3/5

Most market-data and storefront tools are cleanly scoped, but there is meaningful overlap: get_full_board and get_engine_feed are near-duplicates, get_buy_list overlaps with get_morning_brief's candidate list, and get_orders / get_order_status are identical NotOffered stubs. The free/live twin pairs are clearly labeled so agents can distinguish latency/payment intent, but the sheer number of related reads creates selection friction.

Naming Consistency4/5

The large get_* data family is very predictable (get_stock_read, get_stock_read_live, get_rotation, get_rotation_live), and storefront ools use clear verb_noun actions (add_to_cart, remove_from_cart, save_memory). Minor deviations like checkout_handoff and the get_live_setup / get_live_rules naming (which could be misread as *_live twins) keep it from a perfect score.

Tool Count2/5

46 tools is well abovethe 25+ threshold for a coherent toset; at leat13 are direc live twins of free readable plus a 14-tool storefont/memory subdomain. Many could be consoliated into ingle tools with a delay/live param or a single storefront resource, making the surface feel bloated for agents.

Completeness4/5

The market-data surface is very comphehensive: regime, buy-list, hold-state, rotation, sector, stock, crypto day/night/trend/setups, full board, archived board, changes, and engine-feed coverage leave few dead ends for the stated trading-intelligence purpose. Storefont is adequate but has minor acknowledged gaps—orders/order-status are NotOffered stubs and session memories have no update/delete—so it is not a perfect 5.

Resources