Skip to main content
Glama

get_crypto_trend_live

Read-only

Are Bitcoin and Ethereum in an uptrend, as of the newest daily close? The same gate for crypto: whether BTC and ETH are in an uptrend or in cash. Bitcoin and Ethereum trend signal (LONG or CASH per sleeve, 50-day trend gates, BTC 200-day master gate) on the newest completed UTC daily close, evaluated every calendar day including weekends and stamped with the close used (one close ahead of the free tier). Coil Live is a subscription with a 7-day free trial; subscribers connect the Coil Live connector and sign in, and this read returns live data. Agents with an x402 wallet can also pay per call. Without a subscription or an x402 wallet it returns a PaymentRequired object and no data.

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_live"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: weekend-inclusive evaluation, the exact close used, one close ahead of the free tier, and an explicit PaymentRequired object with no data when unauthenticated. Mutating/read semantics match readOnlyHint=true, and the paywall/authentication requirement is exactly the kind of detail annotations cannot convey.

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 core question is front-loaded, which is good, but three sentences restate the same idea ('Are BTC and ETH in an uptrend...', 'The same gate for crypto...', 'Bitcoin and Ethereum trend signal...'). The entitlement and payment details earn their place; the middle restatements do not.

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 zero-param, no-output-schema read tool, it covers freshness, cadence, per-sleeve output values (LONG/CASH), and the failure mode, which is what an agent needs to decide and to interpret a refusal. The success payload's fields beyond the per-sleeve signal are not described, but that is a minor gap given the signals are named.

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?

Zero-parameter tool takes no arguments, so the baseline applies and the schema coverage is already 100%. The description correctly adds nothing spurious about inputs, though it also does not state whether the call scope is configurable (e.g., per-symbol selection) — and it doesn't need to, since the gate is fixed to BTC and ETH.

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 concrete question and resource: BTC/ETH uptrend status per sleeve (LONG or CASH) on the newest completed UTC daily close. The 'live' vs. non-live distinction is implied by 'returns live data' and 'one close ahead of the free tier', but the free sibling get_crypto_trend is never named, so an agent must infer the pairing from the tool name alone.

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 usage context: use it for a live read on the newest completed daily close, evaluated every calendar day including weekends. It also spells out the access paths (Coil Live subscription with 7-day trial, or an x402 wallet for pay-per-call) and the fallback when neither exists. It stops short of explicitly routing to get_crypto_trend for non-live or free access.

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